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?



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Jan 21, 2007 at 01:23:38AM -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?
Not an answer but... People debugging ssh seem to benfit from using
verbose logging (possibly on both sides of the connection) to find
answers.
Cheers,
Kev
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal |mysite.verizon.net/kevin.mark/|
| `. `' Operating System | go to counter.li.org and |
| `- http://www.debian.org/ | be counted! #238656 |
| my keysever: subkeys.pgp.net | my NPO: cfsg.org |

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFsw8+v8UcC1qRZVMRAr0PAJ49OwBxy458eGLkMTzy2e 6wAe3GXACfTwjD
IhphrinbpEIKQ7B5mqfi93Y=
=7e0B
-----END PGP SIGNATURE-----

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBFs6/Q7WZpcbUkaHwRAgZXAKCGdmHnJk6BaCjWAQRZeN9zXdNprACgs tH2
v/Ov7fGUGih9855PqoJTVAk=
=yWPf
-----END PGP SIGNATURE-----

On Sun, Jan 21, 2007 at 01:23:38AM -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?
>
Some things that would us you diagnose the problem:

* the exact command used to generate the key
* an example ssh commandline that works
* an example scp commandline that does not work
* the *exact* errors that you see
* the output of ssh and/or scp with the -v option (or maybe even -vv or
-vvv, depending on whether the first is at all enlightening)

Regards,

-Roberto
--
Roberto C. Sanchez
http://people.connexer.com/~roberto
http://www.connexer.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFtBtG1snWssAFC08RAopHAJ0VzXa9QycbX696PnhUvZ Vrp6SyZwCfbYsX
VY6U5IUsknlh7NkQWDfEBdk=
=q3QR
-----END PGP SIGNATURE-----