hi chuck,
thanks for your information.
i was quite hesistant to delete that line, that was
why i wanted some confirmation.
it is already ok now.
this is not eve.
sorry eve :)
it just happen that i have the same problem that
moment, and while taking some break, i happen to read
this thread. that w
>I don't know what "user account is locked" means, possibly hecause I don't
>know the context in which you got that message.
In the RedHat User Manager, you can choose the Properties of each user and
edit things like what shell they use, change password, enable/disable
account expiration. Also
It's not me! :)
- Eve
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ray Olszewski
Sent: Tuesday, March 15, 2005 11:03 AM
To: linux-newbie@vger.kernel.org
Subject: Re: SOLVED: Some users locked out of ssh and sftp?
If this still you, Eve, just f
If this still you, Eve, just from a different e-mail address? Or is this
someone new with (almost) the same problem as Eve?
At 01:23 AM 3/15/2005 -0800, Donald Duckie wrote:
I got this error message as shown below . . .
How do I change the /root/.ssh/known_hosts file?
It seems encrypted . . .
Ch
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 suces
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 CHANGE
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!
@
@@
At 07:01 PM 3/14/2005 -0500, Eve Atley wrote:
First, I had 'user account is locked'.
Second, once I logged in via the linux box, using 'ssh -l manik
192.168.10.57', it created a new .Xauthority file, apparently.
And they're in.
I hope your problem is solved ... but I'd encourage you to keep an eye
