RE: deny to root .
Hi Evgeny, This *should* work, granted you've gotten the configuration set up correctly. Please give us a bit more info, maybe a dump of your sshd_config would help. Have you restarted the daemon? Brian -Original Message- From: Evgeny Rachlenko [mailto:[EMAIL PROTECTED]] Sent: Monday, August 27, 2001 5:50 AM To: 'Ssh Subject: deny to root . Hello All. I hope it's very simple question :) : How can I deny ssh connection for user root ? PermitRootLogin yes changed to no but ? ? ? -- it doesn't work. :( Sincerely, Evgeny Rachlenko PhoneDo Networks Tel.: +972-9-9517771 ext. 212
RE: wtmp bug on aix
Are we talking OpenSSH or SSH.com? Because, I just checked my OpenSSH install on an AIX 4.3 box and I don't see this symptom. -Ray | -Original Message- | From: Mark Grant [mailto:[EMAIL PROTECTED]] | Sent: Monday, August 27, 2001 1:04 AM | To: [EMAIL PROTECTED] | Subject: wtmp bug on aix | | | Hi, | | I have installed openssh on some AIX 4.3 servers. | There seems to be a bug. | When ever somebody is logged in and using a session the | /var/adm/wtmp file is | filled up with the line sshd. This fills up the /var file | system and creates | huge problems. | | Is there a way I can stop this or is it just a bug ? | I notice it doesn't happen on Solaris. | | | | ** | | | This e-mail and any files transmitted with it are | confidential to Salmat Pty Ltd intended solely for the use of | the individual or entity to whom they are addressed. If you | have received this e-mail in error please return to the | sender and delete from your systems. | | This e-mail message has been swept for the presence of | computer viruses known to Salmat's virus patterns. | | Salmat Pty LtdACN 066 833 458 | | ** | |
SSH key authentication
I am a new OpenSSH user. I need help with OpenSSH. I am able to use password authentication with no problem, but if I try to use the client keys it always defaults to password authentication. I created an identity.pub, id_rsa.pub, and id_dsa.pub and copy all 3 to the authorize-keys file on the remote host in my userid's .ssh directory. If I execute an ssh -v remotehost it only works with the password authentication, it does not try the keys. The sshd_config file includes RSAAuthentication and DSAAuthentication yes on the remote host. I am using all defaults for the ssh_config file for the client. The sshd_config support both ssh1 and sh2. What am I doing wrong ?
RE: SSH key authentication
Title: RE: SSH key authentication copy the authorize-keys to authorize-keys2 and create a config file (man pages) and maybe even a .shosts file(man pages) Jay H. -- From: Wiese, Maria[SMTP:[EMAIL PROTECTED]] Sent: Wednesday, August 29, 2001 12:50 PM To: [EMAIL PROTECTED] Subject: SSH key authentication I am a new OpenSSH user. I need help with OpenSSH. I am able to use password authentication with no problem, but if I try to use the client keys it always defaults to password authentication. I created an identity.pub, id_rsa.pub, and id_dsa.pub and copy all 3 to the authorize-keys file on the remote host in my userid's .ssh directory. If I execute an ssh -v remotehost it only works with the password authentication, it does not try the keys. The sshd_config file includes RSAAuthentication and DSAAuthentication yes on the remote host. I am using all defaults for the ssh_config file for the client. The sshd_config support both ssh1 and sh2. What am I doing wrong ?
RE: SSH key authentication
Title: RE: SSH key authentication Did you add anything to change the order of the authentication? -Mitch -Original Message-From: Jay Huffman [mailto:[EMAIL PROTECTED]]Sent: Wednesday, August 29, 2001 2:40 PMTo: [EMAIL PROTECTED]; 'Wiese, Maria'Subject: RE: SSH key authentication copy the authorize-keys to authorize-keys2 and create a config file (man pages) and maybe even a .shosts file(man pages) Jay H. -- From: Wiese, Maria[SMTP:[EMAIL PROTECTED]] Sent: Wednesday, August 29, 2001 12:50 PM To: [EMAIL PROTECTED] Subject: SSH key authentication I am a new OpenSSH user. I need help with OpenSSH. I am able to use password authentication with no problem, but if I try to use the client keys it always defaults to password authentication. I created an identity.pub, id_rsa.pub, and id_dsa.pub and copy all 3 to the authorize-keys file on the remote host in my userid's .ssh directory. If I execute an ssh -v remotehost it only works with the password authentication, it does not try the keys. The sshd_config file includes RSAAuthentication and DSAAuthentication yes on the remote host. I am using all defaults for the ssh_config file for the client. The sshd_config support both ssh1 and sh2. What am I doing wrong ?
SSH 2.0.12 scp2 wont talk to OpenSSH scp
A Solaris 2.6 machine sporting version 2.0.12 of SSH, using protocol 2 public key authentication (no problem) refuses to talk protocol 2 for an scp operation with an OpenSSH client, version 2.9, running on Solaris 8, transferring the file by protocol 1 instead (according to the messages). Protocol 2 seems to work for all other purposes (including, evidently, sftp according to the debug3 statements on file transfers). I live on the Solaris 8 box. On the 2.6 machine, /usr/local/bin/scp is a symlink to scp2. A (names changed to protect the innocent) copy of an scp session follows. It tells the tale. scp -v name@address.hidden:/home/name/temp/testfile.txt . Executing: program /usr/local/bin/ssh host address.hidden, user name, command scp -v -f /home/name/temp/testfile.txt warning: Development-time debugging not compiled in. warning: To enable, configure with --enable-debug and recompile. warning: Executing scp1 compatibility. Sending file modes: C0644 11 testfile.txt testfile.txt 100% ||11 00:00 The file is transferred successfully. Absent -v, I'm a bit strapped to diagnose the problem. Apart from persuading these folks to upgrade to a more current ssh (politically unlikely), I'm about stuck on getting scp to work in v2 mode. I'm guessing a bit at the remote ssh version number, but ssh -v -l name address.hidden ls says (in part) : debug1: Remote protocol version 1.99, remote software version 2.0.12 (non-commercial) Suggestions welcome. More debug output available if there's any interest.