public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: SOTL <sotl155360@earthlink.net>
To: Donald Duckie <schipperke2000@yahoo.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: SOLVED: Some users locked out of ssh and sftp?
Date: Tue, 15 Mar 2005 08:49:15 -0500	[thread overview]
Message-ID: <200503150849.16266.sotl155360@earthlink.net> (raw)
In-Reply-To: <20050315092308.63122.qmail@web53603.mail.yahoo.com>

On Tuesday 15 March 2005 04:23, Donald Duckie wrote:
> I got this error message as shown below  . . .
> How do I change the /root/.ssh/known_hosts file?
> It seems encrypted . . .
>
>
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @    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
> 23:52:d4:e8:6a:75:72:ed:78:cb:31:1f:6a:ff:b4:ea.
> Please contact your system administrator.
> Add correct host key in /root/.ssh/known_hosts to get
> rid of this message.
> Offending key in /root/.ssh/known_hosts:7
> RSA host key for 192.168.0.1 has changed and you have
> requested strict checking.
> Host key verification failed.
>
I posted this to you several days ago.

The file you are seeking is located in the computer you are loging in FROM not 
the server.

Look at my previous message:

Hi All

I just spent half a day trying to fix this problem on the wrong computer. In 
justification of the time I was not using SSH directly but fish which uses 
SSH so I was not getting the error messages. Once I tried it connecting using 
SSH I fixed the problem in 5 minutes

In Linux SSH has a computer verification file for computers that have 
permission to log in at /home/<user>/.ssh/known_hosts:2

Explanation. I trashed the HD in one box [a test box with no data in it]. 
After re installation of HD, & configuration I found that I could SSH from 
the  new system but could not SSH from computers which had previously 
connected to the box with the new HD and system. 

I removed contents of above fine saved and was able to immediately log-in.

Hope this helps.

Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2005-03-15 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6667>
2005-03-15  9:23 ` SOLVED: Some users locked out of ssh and sftp? Donald Duckie
2005-03-15 13:49   ` SOTL [this message]
2005-03-15 14:54   ` chuck gelm
2005-03-15 16:02   ` Ray Olszewski
2005-03-15 16:14     ` Eve Atley
2005-03-16  2:13 Donald Duckie
  -- strict thread matches above, loose matches on Subject: below --
2005-03-14 21:54 Eve Atley
2005-03-15  0:01 ` SOLVED: " Eve Atley
2005-03-15  0:06   ` Ray Olszewski
2005-03-15 16:16     ` Eve Atley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200503150849.16266.sotl155360@earthlink.net \
    --to=sotl155360@earthlink.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=schipperke2000@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox