Hello, The commercial SSH and OpenSSH store their keys under different directories $HOME/.ssh2 and $HOME/.ssh respectively. In your non-working case (TRU64->RHEL4), I had to do the following to convert the commercial ssh key on the OpenSSH server:
ssh-keygen -i -f id_dsa_2048_comssh.pub > ~/.ssh/authorized_keys2 Your mileage may vary but it may also be useful to run your daemon and client in verbose mode in order to get more debug information as there are lots of reasons why this might not work.. :( I hope this helps, Vincent Quoting [EMAIL PROTECTED]: > Hello, > > I have an issue that has me baffled. I am trying to setup SSH-key > authentication between TRU64 V5.1B and Red Hat Enterprise Linux (RHEL4 > update6). I want the TRU64 box the authenticate via SSH-keys "no > password" within a > script TRU64 to RHEL4. > > We are abondoning TRU64 unix in favor of RHEL4 and RHEL5. My > particular need right now is RHEL4. > > I understand the basic differences of the SSH versions: > > TRU64 --> SSH2 (commercial) > RHEL4 --> SSH (open ssh) > > I can get the following SSH-Key authentication (login without > password) to work just fine: > > TRU64 to TRU64 > RHEL4 to RHEL4 > RHEL4 to TRU64 > > I cannot get TRU64 to authenticate to RHEL4 "No password neded". > Anyone have any > thoughts/ideas? Any help greatly appreciated. > > Steve > > Stephen L. LaBelle > Metropolitan State College of Denver > Senior System Administrator > Database Administration Team > [EMAIL PROTECTED] > 303-556-3644 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
