Re: Problems with scp and cron

From: Robert Nickel (Robert_Nickel_at_bigfoot.com)
Date: 10/21/04 

Date: Thu, 21 Oct 2004 08:59:18 +0200

Darren Dunham wrote:
> Robert Nickel <Robert_Nickel@bigfoot.com> wrote:
>
>>>Is the file itself local or on an NFS server of some sort?
>>
>>no, its in my home-dir
>
>
> Which could of course be on an NFS server, but I suppose you're saying
> that it's not.
It really is not. This partition is on my local hard disk.

>
>
>>debug1: Trying private key: /home/robert/.ssh2/identification
>>debug1: PEM_read_PrivateKey failed
>>debug1: read PEM private key done: type <unknown>
>
>
> Are you sure you really have a .ssh2/identification file (instead of a
> .ssh2/identity file)?
Yes. I have checked this again. And the permissions of the
identification are rw for me only and the .ssh2-dir is readable to anyone.

> Why are you specifying that on the command line
> explicitly instead of just letting it use the defaults?
It does not make a difference. I also tried leaving the files with
default names (identity) in .ssh directory. Then the output reads

debug1: Trying private key: /home/robert/.ssh/identity
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: Trying private key: /home/robert/.ssh/id_rsa
debug1: Trying private key: /home/robert/.ssh/id_dsa
debug1: Next authentication method: password

Do I need a different format of the key file?

I am confused that it works when I run it manually

But I considered something strange:
When I run the script manually, ssh finds the identification file in .ssh2/
But from the cron-job ssh looks for .ssh/identity or dsa or rsa in this
directory.
Do I have to set soe path?

Robert

>

Relevant Pages

  • Re: cant connect, ssh hangs after SSH2_MSG_KEX_DH_GEX_GROUP
    ... Looks like the sshd is not getting the ssh key request from the client ... debug1: Connecting to server port 22. ... debug1: read PEM private key done: type DSA ...
    (SSH)
  • New S10 system does not accept ssh from other hosts
    ... debug1: read PEM private key done: type RSA ... debug1: private host key: #0 type 1 RSA ... When I try to ssh in, or even telnet to port 22, from ...
    (comp.unix.solaris)
  • Re: cant connect, ssh hangs after SSH2_MSG_KEX_DH_GEX_GROUP
    ... cant connect, ssh hangs after SSH2_MSG_KEX_DH_GEX_GROUP ... debug1: Connecting to server port 22. ... debug1: read PEM private key done: type DSA ... debug3: ...
    (SSH)
  • ssh cant connect localhost?
    ... OpenSSH_3.2.2p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f ... I generate rsa and dsa keys since I don't which is in need. ... debug1: Rhosts Authentication disabled, originating port will not be trusted. ... debug1: read PEM private key done: type DSA ...
    (comp.security.ssh)
  • ssh cant connect localhost?
    ... OpenSSH_3.2.2p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f ... I generate rsa and dsa keys since I don't which is in need. ... debug1: Rhosts Authentication disabled, originating port will not be trusted. ... debug1: read PEM private key done: type DSA ...
    (comp.security.ssh)