From: chuck gelm <chuck@gelm.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 09:54:10 -0500 [thread overview]
Message-ID: <4236F712.6000508@gelm.net> (raw)
In-Reply-To: <20050315092308.63122.qmail@web53603.mail.yahoo.com>
Donald Duckie wrote:
> I got this error message as shown below . . .
> How do I change the /root/.ssh/known_hosts file?
> It seems encrypted . . .
Hi, Donald:
The file is not encripted, but it contains an encription key for
each remote hostname. There is a line for each 'ssh' host that
you have sucessfully connected. If the remote 'host' has changed
its encription key and you already have a line with the old
encription key, 'ssh' will fail with that message.
Solution:
Use a 'text' editor and open /root/.ssh/known_hosts.
Delete the line that starts with the remote hostname.
Save and exit. (or 'rm known_hosts')
'ssh' to that hostname.
Answer 'yes' when prompted.
HTH, Chuck
-
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
next prev parent reply other threads:[~2005-03-15 14:54 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
2005-03-15 14:54 ` chuck gelm [this message]
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=4236F712.6000508@gelm.net \
--to=chuck@gelm.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