- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ssh not populating known_host file
Operating System - HP-UX
1752661
Members
5396
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2009 10:48 AM
11-05-2009 10:48 AM
Re: ssh not populating known_host file
OK..here goes:
For those who may hit this some day.
Secure Shell (ssd) version 4.50 does not populate known_hosts file as Stephen mentions. Closest version that works 4.40
FYI...that pesky chroot issue shows up after 4.20 version and is still there at ver 5.10. I don't know what version they ever got that fixed yet.
With that said. Went on testbox and downgraded to v4.40 and now it would populate the known_host for me. But still was having issue in both directions where the passwd prompt kept coming up. Then, because the Windows guy wouldn't give me that accounts password, he was handling doing the 'ftp' of the id_rsa.pub files. I didn't care if UNIX created them or Windows generated the key. What I discovered was, since he was doing this from his laptop, the files got corrupted in the transfer. When I watched him close and asked to type 'binary' before he 'puts' the file over...voila a measure of success. He ftp'd in binary the file to my UNIX box he generated and I set it in the authorized_keys file also. Now he could connected passwordless to the UNIX box. But UNIX could not do a passwordless connection to Windows. We looked at a couple setting on the Windows ssh_config files and noticed there are setting he should change to make it possible for passwordless. So once he makes those changes we can go both ways.
For now...I don't care cause for production I only need for him to move the files TO UNIX, so I'll just test for return connectivity another time and get that resolved. I'm working the way I need...
Hope my ramblings made some sense.
My issue is fixed and I thank you all for your contributions. They really did help!
Points a comin!
Rita
For those who may hit this some day.
Secure Shell (ssd) version 4.50 does not populate known_hosts file as Stephen mentions. Closest version that works 4.40
FYI...that pesky chroot issue shows up after 4.20 version and is still there at ver 5.10. I don't know what version they ever got that fixed yet.
With that said. Went on testbox and downgraded to v4.40 and now it would populate the known_host for me. But still was having issue in both directions where the passwd prompt kept coming up. Then, because the Windows guy wouldn't give me that accounts password, he was handling doing the 'ftp' of the id_rsa.pub files. I didn't care if UNIX created them or Windows generated the key. What I discovered was, since he was doing this from his laptop, the files got corrupted in the transfer. When I watched him close and asked to type 'binary' before he 'puts' the file over...voila a measure of success. He ftp'd in binary the file to my UNIX box he generated and I set it in the authorized_keys file also. Now he could connected passwordless to the UNIX box. But UNIX could not do a passwordless connection to Windows. We looked at a couple setting on the Windows ssh_config files and noticed there are setting he should change to make it possible for passwordless. So once he makes those changes we can go both ways.
For now...I don't care cause for production I only need for him to move the files TO UNIX, so I'll just test for return connectivity another time and get that resolved. I'm working the way I need...
Hope my ramblings made some sense.
My issue is fixed and I thank you all for your contributions. They really did help!
Points a comin!
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2009 10:51 AM
11-05-2009 10:51 AM
Re: ssh not populating known_host file
THREAD CLOSED
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP