Everything through an ssh connection is encrypted, even username/password. So I dont see if there should be anything more secure than that..
Is connecting to an ssh server using username and password secure? Are there any more secure way of connecting to an ssh server?
Everything through an ssh connection is encrypted, even username/password. So I dont see if there should be anything more secure than that..
No possibillity to un-encrypt it?
Only with the correct keys that the ssh session is using at the exact moment.
Trust the SSH. It is your friend. Where others speak too loudly, SSH whispers. SSH is so much more secure than TELNET or RSH, its riduiculous. I literally swear by ssh.
[quote author=-JhAzEr- link=board=5;threadid=4955;start=0#49308 date=1031990183]
Are there any more secure way of connecting to an ssh server?
[/quote]
Use digital authentication keys such as from RSA.
I agree. SSH is the most secure thing for remote logging right now. Trust it and no other...
No such thing as password cracking, like john the ripper does in /etc/passwd?
I've never heard of a program that would do it. It would be practically impossible.
This is from man ssh:
I cant remember, but isnt it either a 128 bit or a 512 bit alphanumeric key?Code:ssh supports RSA based authentication. The scheme is based on public-key cryptography: there are cryptosystems where encryption and decryption are done using separate keys, and it is not possible to derive the decryption key from the encryption key. RSA is one such system. The idea is that each user creates a public/private key pair for authentication purposes. The server knows the public key, and only the user knows the private key. The file $HOME/.ssh/authorized_keys lists the public keys that are permitted for logging in. When the user logs in, the ssh program tells the server which key pair it would like to use for authentication. The server checks if this key is permitted, and if so, sends the user (actually the ssh program running on behalf of the user) a challenge, a random number, encrypted by the user's public key. The challenge can only be decrypted using the proper private key. The user's client then decrypts the chal- lenge using the private key, proving that he/she knows the private key but without disclosing it to the server.
Bookmarks