On Sun, 2007-01-21 at 01:23 -0500, Jude DaShiell wrote:
> Earlier I set up a private key with ssh -keygen and copied it to the
> proper place on my isp's computer for me to use. That works fine with ssh
> but breaks with scp since scp says the key is too long and doesn't grant
> access to the other machine. Could the pass phrase be too long for scp?
The biggest problem that occur with ssh/scp/etc:
1. Wrong permissions on the file the public part of the key pair is
in on the remote machine.
2. The name of the file the key is in, is incorrect.
3. Putting the private part of the key on the remote machine.
Fixing these problems are 95% of the answer.
Answers to these:
1. For BSD's OpenSSH on Debian, the perms need to be "chmod 0600"
2. $HOMEDIR/.ssh/authorized_keys
3. Copy the public part (id_dsa.pub) of the key pair to the machine
the "cat $HOMEDIRid_dsa.pub > $HOMEDIR/.ssh/authorized_keys |
chmod 0600 $HOMEDIR/.ssh/authorized_keys | rm
$HOMEDIR/id_dsa.pub"
That should take care of you issue, unless the ISP is using something
other than BSD's OpenSSH.
--
greg, greg@gregfolkert.net
The technology that is
Stronger, better, faster: Linux
Attachment:
signature.asc
Description: This is a digitally signed message part