Hi, i am not using ssh2 for now, only ssh1. i figured that it'll be good to debug ssh1 before i'll call it from within ssh2. and you right, it's very weird that i do not get any error messages at all. it's almost like this suppose to happen. but may be i am emulating an attack, unknowingly? originally i wanted to set it so publickey and password auth will be used together, but i do not get the to password phase and my keys, apparently, are not working. i tried making new identity file and registered it in ~/.authorized_keys file on the server, but no luck, i do not get far enough to look into users ~/.authorised_keys i narrowed it down to this: 1) after generating new hostkey, my client asks whether i would like to register new server key or not, so i am connecting to sshd1, they agree on protocols and versions server: log: Connection from 192.168.2.2 port 4534 client: SSH: connected 2) if i don't save new server key, connection terminates with this line (RCVD), which is expected server: debug: Sent 2176 bit public key and 2048 bit host key client: SSH: connected SSH: RCVD: server public key 3) if i accept new server key connection terminates on the next line (SEND): client: SSH: connected SSH: RCVD: server public key SSH: SEND: session key server: fatal: Connection closed by remote host the behavior does not change whether i use session key(rsa 2048 bit) or not thanks for ur help, alex P.S. here is my sshd1_config file: # This is ssh server systemwide configuration file. Port 32500 ListenAddress 0.0.0.0 #ListenAddress 192.168.1.1:24.19.120.119 # PidFile /var/run/sshd1.pid HostKey /etc/ssh1/ssh1_hostkey RandomSeed /etc/ssh1/ssh1_random_seed ServerKeyBits 2048 #Compression yes #CompressionLevel 9 LoginGraceTime 60 KeyRegenerationInterval 3600 PermitRootLogin no IgnoreRhosts yes # StrictModes no X11Forwarding no X11DisplayOffset 10 PrintMotd yes CheckMail yes KeepAlive yes Umask 032 SyslogFacility AUTH # RhostsAuthentication no RhostsRSAAuthentication no RSAAuthentication yes PasswordAuthentication yes #AllowedAuthentications publickey,password #RequiredAuthentications password PermitEmptyPasswords no # UseLogin no # AllowHosts *.our.com friend.other.com # DenyHosts lowsecurity.theirs.com *.evil.org evil.org SilentDeny no "Gonyou, Austin" wrote: > I see you are using secure CRT. Try setting the ssh type as standard, > instead of datafellows. Do you get any error types at all? > > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-796-9023 > email: [EMAIL PROTECTED] > > > -----Original Message----- > > From: Aleksander V. Mazlov [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, September 02, 2001 6:18 PM > > To: [EMAIL PROTECTED] > > Subject: ssh1 login problem > > > > > > hi, > > i have upgraded my ssh1 to 1.2.31 and got locked out of my box. > > i am using 2048-RSA hostkey's > > > > when i try to connect to my box (using SecureCRT from VanDuke) i get > > only this far(on the client side): > > SSH: connected > > SSH: RCVD: server public key > > SSH: SEND: session key > > > > after that i get a message in my logs saying connection > > closed by remote > > host. if i ssh1 to another account on localhost interface everything > > works fine. > > > > did anyone have a similar problem? any ideas what might be wrong? > > > > i never even get to password authentication, so does that mean my RSA > > identity files are wrong? i tried with and without them on my client > > side and got the same results. > > > > don't know where to look for the problem? any ideas? > > > > thanks, > > alex > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
