Fernando de Oliveira wrote: > --- Em qua, 3/4/13, Ken Moffat escreveu: > >> De: Ken Moffat >> Assunto: Re: [blfs-support] openssh-6.2p1 messages >> Para: "BLFS Support List" >> Data: Quarta-feira, 3 de Abril de 2013, 3:10 >> On Wed, Apr 03, 2013 at 12:14:35AM >> -0500, Bruce Dubbs wrote: >>> Ken Moffat wrote: >>> >>>> Thanks, Bruce. On the server [ 6.0p1 ] I >> have >>> >>>> AuthorizedKeysFile >> .ssh/authorized_keys >>> >>> This means nothing on the server. Is >> it in /etc/ssh/sshd_cpnfig? >>> >> yes, on the server in sshd_config I have >> >> AuthorizedKeysFile .ssh/authorized_keys >>>> Subsystem >> sftp /usr/sbin/sftp-server >>>> PermitRootLogin no >>>> >>>> On the desktop I don't have any >> config in ~/.ssh/ >>> >>> That's optional. In many cases I needed to log on >> as a different user >>> and sometimes had issues with networrk timeouts >> (ServerAlive*). I like >>> to disable sshv1 also since it's not secure. >>> >>> >>>> ssh -v gives me a lot of >> information, finishing with >>>> debug1: Next authentication method: publickey >>>> debug1: Trying private key: /home/ken/.ssh/id_rsa >>> >>> See >>> http://security.stackexchange.com/questions/5096/rsa-vs-dsa-for-ssh-authentication-keys >>> >>> Be sure to read the responses. >>> >>> I use dsa because of the the (now obsolete) patent >> issues and I don't >>> need to change for my purposes. >>> >> >> It seems good enough for me. >> >>>> no such identity: /home/ken/.ssh/id_rsa: No such >> file or directory >>>> debug1: Offering DSA public key: >> /home/ken/.ssh/id_dsa >>> >>> It looks like that's not being accepted. Do you >> have id_dsa.pub in the >>> remote ~/.ssh/authorized_keys? >>> >> No, it's in ~/.ssh/ itself. >> >> Thanks anyway. >> >> ĸen >> -- >> das eine Mal als Tragödie, das andere Mal als Farce > > Perhaps you might find this useful. > > I have had this problem in a VM running ArchLinux, using rsync (over > ssh). > > Messages: > > no such identity: /home/USER/.ssh/id_rsa: No such file or directory > no such identity: /home/USER/.ssh/id_dsa: No such file or directory > no such identity: /home/USER/.ssh/id_ecdsa: No such file or directory > > Solved by using > > cat >> ~/.ssh/config << "EOF" > LogLevel ERROR > EOF > chmod -v 0600 ~/.ssh/config
That looks like the output is coming from syslogd. Look at /etc/syslog.conf to see if anything is outputting from there. Tuning ssh's log level is a good idea too. The default is INFO. The levels of security vary a bit. You can create a key without a pass phrase, use ssh-agent, or manually type in a pass phrase every time you want to use a key. Then there is the type of key and the key length that can be varied. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
