Do you have a question? Post it now! No Registration Necessary. Now with pictures!
March 2, 2009, 11:53 pm
rate this thread
scp file userA@remote_host:/path/to/file
I am not prompted for a passwd and the transfer succeeds.
If I am not userA and I issue the same command I am prompted for
userA's passwd. Why is this? In both cases I am accessing remote_host
as userA. Is there a way around this?
Re: scp question
So either remote_host is set to trust your local host's authentication of
identity (so it trusts that local_host has already checked that you're really
userA, and remote_host doesn't have to), OR you've got a key in your .ssh
Because you're not userA. You're trying to log on as someone for whom you
haven't already authenticated.
In one case userA is trying to access as userA, in the other some impostor is
trying to access as userA. I'd hope there to be different behaviors.
Yes. You can set up a key for userB that is in the authorization list for
userA on remote_host.
Mark Rafn email@example.com <http://www.dagon.net/
Re: scp question
Because one of the public keys contained in the remote
~userA/.ssh/authorized_keys file has the corresponding private key in
the local ~userA/.ssh directory, but not in the ~/.ssh directory of
the other user you're trying to do this as.
Place a private key in the ~/.ssh directory of the other user you want to
do this as and append a line for the corresponding public key in
~userA/.ssh/authorized_keys in the remote system. Give serious thought
to protecting the private keys for both userA and the other user with a
passphrase, as leaving them unencrypted is severe security weakness.
Thank you for noticing this new notice
Your noticing it has been noted
And will be reported to the authorities
- » plink/putty remote command not working as expected
- — Previous thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum