HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SSH without password request
Operating System - HP-UX
1827444
Members
5891
Online
109965
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
Forums
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
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-14-2008 03:59 AM
11-14-2008 03:59 AM
I have set the authorized_keys for a unix account to connect via ssh from server1 to server2 without requesting password.
everything is Ok...BUT when a try the first connection I get, when i try the second connection appears this message:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for svuxger1 has changed,
and the key for the according IP address 10.200.1.240
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /home/getusers/.ssh/known_hosts:74
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
ff:fe:03:57:33:77:37:ff:02:5c:2d:45:06:5d:1c:33.
Please contact your system administrator.
Add correct host key in /home/getusers/.ssh/known_hosts to get rid of this message.
Offending key in /home/getusers/.ssh/known_hosts:73
RSA host key for svuxger1 has changed and you have requested strict checking.
Host key verification failed.
when a try the third connection I get and when I try the fourth connection that message appears again...and it happen every time.
How Can I solve it???
Thank you since now
everything is Ok...BUT when a try the first connection I get, when i try the second connection appears this message:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for svuxger1 has changed,
and the key for the according IP address 10.200.1.240
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /home/getusers/.ssh/known_hosts:74
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
ff:fe:03:57:33:77:37:ff:02:5c:2d:45:06:5d:1c:33.
Please contact your system administrator.
Add correct host key in /home/getusers/.ssh/known_hosts to get rid of this message.
Offending key in /home/getusers/.ssh/known_hosts:73
RSA host key for svuxger1 has changed and you have requested strict checking.
Host key verification failed.
when a try the third connection I get and when I try the fourth connection that message appears again...and it happen every time.
How Can I solve it???
Thank you since now
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2008 04:10 AM
11-14-2008 04:10 AM
Solution
Hi Gustavo,
First check if there was an IP- or namechange on the target host.
if so:
remove the offending keys from known_hosts file:
Here: Simply delete line number 73 and 74 from file /home/getusers/.ssh/known_hosts
And then try again.
You have to add the new key by typing yes when you were asked to.
rgds
HGH
First check if there was an IP- or namechange on the target host.
if so:
remove the offending keys from known_hosts file:
Here: Simply delete line number 73 and 74 from file /home/getusers/.ssh/known_hosts
And then try again.
You have to add the new key by typing yes when you were asked to.
rgds
HGH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2008 04:19 AM
11-14-2008 04:19 AM
Re: SSH without password request
Thank you Hemmetter,
You are right....now I understood and I fixed the problem ...
I had two IPs set into the server2...
Bye
You are right....now I understood and I fixed the problem ...
I had two IPs set into the server2...
Bye
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP