Hot answers tagged

11

Yes. The password is sent over the encrypted connection, but it's in plaintext to the remote server. The usual way to authenticate is for the server to calculate a hash of the password and to compare it to a value saved on the server. There are several ways of saving hashes, and with current implementations, the client doesn't know what the server uses. (...


3

If you're using password authentication, then SSH sends the password over the network. The connection is encrypted, so eavesdroppers can't see the password. The connection is authenticated, provided that you don't click blindly through a “The authenticity of … can't be established” message, so your password won't be sent to anyone except the legitimate ...


3

If you use a password based authentication scheme then, yes the password is passed over the network to the end point... But it is an encrypted channel. eg % ssh remotehost user@remotehost's password: bash$ logout In this scenario the password was sent encrypted over the network. This is why it is very important to handle known_hosts entries properly ...


2

Yes, rsync is your best bet. Something like this should work: rsync -vr --size-only --times <source> <dest> --size-only tells rsync not to copy the files again, --times tells it to update timestamps.


2

Yes, ssh sends the password over the network, but after end-to-end encryption has been negotiated. See section 8 of RFC 4252 which says that a password authentication message contains plaintext password in ISO-10646 UTF-8 encoding [RFC3629]


1

This probably isn't the answer you want to hear, but you can't do what you're trying to do. The ProxyCommand option in ssh expects to STDIN & STDOUT of the command to be connected directly to the destination host (%h) and port (%p). Thus it is the local ssh process which is talking to the remote sshd, not the proxy host's ssh process. And since it's the ...


1

you can enable verbose more logging for sshd: sudo nano /etc/ssh/sshd_config add line LogLevel VERBOSE and restart sshd sudo systemctl restart ssh view log entry journalctl -u sshd |tail -100



Only top voted, non community-wiki answers of a minimum length are eligible