Reputation: 41
Unable to connect, And not sure how many ways I can type "bandit0" for a password
Upvotes: -5
Views: 11130
Reputation: 1
I faced the same problem.
I was usig ssh bandit.labs.overthewire.org -p 2220
then it was connecting to kali@bandit.labs.overthewire.org. But we are supposed to connect to server with username bandit0.
Now, we have to explicitly write the username in the ssh command.
SO, the command is ssh [email protected] -p 2220
. Now, look the server you connected is bandit0, not kali. Use password: bandit0.
Congratulations, you just connected to the Server.
Upvotes: 0
Reputation: 13
The login issue also can occur when you have existing ssh identities(ssh keys in ~/.ssh/
), with
ssh [email protected] -p 2220
# or
sshpass -p 'bandit0' ssh [email protected] -p 2220
every single attempt results in the following, without the option to even put password
_ _ _ _
| |__ __ _ _ __ __| (_) |_
| '_ \ / _` | '_ \ / _` | | __|
| |_) | (_| | | | | (_| | | |_
|_.__/ \__,_|_| |_|\__,_|_|\__|
This is an OverTheWire game server.
More information on http://www.overthewire.org/wargames
[email protected]: Permission denied (publickey,password).
If you go and remove the last entry in ~/.ssh/known_hosts
then you'll be greeted with a yes/no/[fingerprint]
option again, but nothing changes
The solution here is to enforce password authorization:
... -o PubkeyAuthentication=no -o PreferredAuthentications=password ...
Upvotes: 0
Reputation: 1
ssh -p 2220 [email protected]
password: bandit0
Highly Recommend! "This command should work by adding '0' between 'bandit' and '@'."
Upvotes: -1
Reputation: 101
Can you try logging in using this exact command
ssh -p 2220 [email protected]
Password: bandit0
This should work
Upvotes: 2
Reputation: 21
if you do not have this problem "Too many authentication failures", use this:
ssh [email protected] -p 2220
if you are a windows user, it is better to use PuTTY than cmd.exe to play this game:
host name: bandit.labs.overthewire.org
port: 2220
open
login as: bandit0
password: bandit0
done
Upvotes: 0
Reputation: 41
ssh is not telnet with its general syntax of telnet server port. I believe even in Windows the basic usage of ssh is like:
ssh [-p port] [user@]server [command]
You did ssh [email protected] 2220. You connected to the default port (22) and 2220 was the command.
It so happens there is a server on port 22, but this is not the server that accepts the credentials you know.
The command 2220 was never invoked because you failed to authenticate in the first place. Instead of 2220 it could have been anything, it wouldn't be invoked either.
You want to connect like this:
ssh -p 2220 [email protected]
Upvotes: 0