Re: SOLVED: Some users locked out of ssh and sftp?

Re: SOLVED: Some users locked out of ssh and sftp?

[Donald Duckie]

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.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-
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

Re: SOLVED: Some users locked out of ssh and sftp?

[SOTL]

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

Re: SOLVED: Some users locked out of ssh and sftp?

[chuck gelm]

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

Re: SOLVED: Some users locked out of ssh and sftp?

[Ray Olszewski]

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 . . .

Chuck identified the right first-pass fix here. To expand a bit: go into 
the known_hosts file (on the client end, NOT the server end), find the 
entry for the target sshd server's system (at the START of each long entry 
is one or more identifiers, which could be hostnames, FQDNs, or IP 
addresses ... look for 192.168.0.1) and simply delete it. Then your ssh 
client will see the connection attempt as a first connection to a new host 
and ask you to confirm it manually ... at which point it will do the 
required update to known_hosts for you.

The above may not work in your setup, though; as I read the man page, it is 
unclear how ssh handles new connections when set to "StrictHostKeyChecking 
Yes". If this does NOT work, I suggest a second approach below.


>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>@    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.

What is causing your problem is that you (probably) have

         StrictHostKeyChecking Yes

in your ssh **client's** config file (/etc/ssh/ssh_config for systemwide 
settings,  $HOME/.ssh/config for user-specific setting). Change this 
setting to

         StrictHostKeyChecking Ask

and ssh will ask you if you want to update the key when it sees this sort 
of thing, which occurred either because you reinstalled sshd on the host in 
question (thereby generating a new server key in 
/etc/ssh/ssh_host_rsa_key), or you replaced the host at that hostname, 
FQDN, or IP address (whichever way you attempted to connect to it ... 
probably IP address, since the message refers to 192.168.0.1).


-
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

RE: SOLVED: Some users locked out of ssh and sftp?

[Eve Atley]

It's not me! :)

- Eve

-----Original Message-----
From: linux-newbie-owner@vger.kernel.org
[mailto:linux-newbie-owner@vger.kernel.org] 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 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 . . .

Chuck identified the right first-pass fix here. To expand a bit: go into 
the known_hosts file (on the client end, NOT the server end), find the 
entry for the target sshd server's system (at the START of each long entry 
is one or more identifiers, which could be hostnames, FQDNs, or IP 
addresses ... look for 192.168.0.1) and simply delete it. Then your ssh 
client will see the connection attempt as a first connection to a new host 
and ask you to confirm it manually ... at which point it will do the 
required update to known_hosts for you.

The above may not work in your setup, though; as I read the man page, it is 
unclear how ssh handles new connections when set to "StrictHostKeyChecking 
Yes". If this does NOT work, I suggest a second approach below.


>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>@    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.

What is causing your problem is that you (probably) have

         StrictHostKeyChecking Yes

in your ssh **client's** config file (/etc/ssh/ssh_config for systemwide 
settings,  $HOME/.ssh/config for user-specific setting). Change this 
setting to

         StrictHostKeyChecking Ask

and ssh will ask you if you want to update the key when it sees this sort 
of thing, which occurred either because you reinstalled sshd on the host in 
question (thereby generating a new server key in 
/etc/ssh/ssh_host_rsa_key), or you replaced the host at that hostname, 
FQDN, or IP address (whichever way you attempted to connect to it ... 
probably IP address, since the message refers to 192.168.0.1).


-
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

-
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

Re: SOLVED: Some users locked out of ssh and sftp?

[Donald Duckie]

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 was why i asked as to how i would
modify the known_hosts file.

donald

--- chuck gelm <chuck@gelm.net> wrote:
> 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
> 


		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 
-
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

RE: Some users locked out of ssh and sftp?

[Eve Atley]

Thanks for the info on locate; I didn't realize it was database-driven.
More details on the SSH issue here. I checked the session log for WinSCP and
here are the results. 
I will include here a non-working session (keyur@local) as well as a working
session (gagan@local).


NON-WORKING
--------------------------------

. 2005-03-14 16:48:22.233
--------------------------------------------------------------------------
. 2005-03-14 16:48:22.233 WinSCP Version 3.7.3 (Build 265) (OS 5.0.2195
Service Pack 4)
. 2005-03-14 16:48:22.233 Login time: Monday, March 14, 2005 4:48:22 PM
. 2005-03-14 16:48:22.233
--------------------------------------------------------------------------
. 2005-03-14 16:48:22.233 Session name: keyur@local
. 2005-03-14 16:48:22.233 Host name: 192.168.10.57 (Port: 22)
. 2005-03-14 16:48:22.233 User name: keyur (Password: Yes, Key file: No)
. 2005-03-14 16:48:22.233 Transfer Protocol: SFTP (SCP)
. 2005-03-14 16:48:22.233 SSH protocol version: 2; Compression: No
. 2005-03-14 16:48:22.233 Agent forwarding: No; TIS/CryptoCard: No; KI: Yes;
GSSAPI: No
. 2005-03-14 16:48:22.233 Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. 2005-03-14 16:48:22.233 Ping type: -, Ping interval: 30 sec; Timeout: 15
sec
. 2005-03-14 16:48:22.233 SSH Bugs: -,-,-,-,-,-,-,-
. 2005-03-14 16:48:22.243 SFTP Bugs: -,-
. 2005-03-14 16:48:22.243 Proxy: none
. 2005-03-14 16:48:22.243 Return code variable: Autodetect; Lookup user
groups: Yes
. 2005-03-14 16:48:22.243 Shell: default, EOL: 0
. 2005-03-14 16:48:22.243 Local directory: default, Remote directory: home,
Update: No, Cache: Yes
. 2005-03-14 16:48:22.243 Cache directory changes: Yes, Permanent: Yes
. 2005-03-14 16:48:22.243 Clear aliases: Yes, Unset nat.vars: Yes, Resolve
symlinks: Yes
. 2005-03-14 16:48:22.243 Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. 2005-03-14 16:48:22.243
--------------------------------------------------------------------------
. 2005-03-14 16:48:22.243 Looking up host "192.168.10.57"
. 2005-03-14 16:48:22.243 Connecting to 192.168.10.57 port 22
. 2005-03-14 16:48:22.253 Server version: SSH-1.99-OpenSSH_3.5p1
. 2005-03-14 16:48:22.253 We claim version: SSH-2.0-WinSCP_release_3.7.3
. 2005-03-14 16:48:22.253 Using SSH protocol version 2
. 2005-03-14 16:48:22.263 Doing Diffie-Hellman group exchange
. 2005-03-14 16:48:22.303 Doing Diffie-Hellman key exchange
. 2005-03-14 16:48:25.127 Host key fingerprint is:
. 2005-03-14 16:48:25.127 ssh-rsa 1024
70:ea:61:3a:cb:96:f9:02:3b:99:4f:81:da:93:a1:06
. 2005-03-14 16:48:25.137 Initialised AES-256 client->server encryption
. 2005-03-14 16:48:25.137 Initialised HMAC-SHA1 client->server MAC algorithm
. 2005-03-14 16:48:25.137 Initialised AES-256 server->client encryption
. 2005-03-14 16:48:25.137 Initialised HMAC-SHA1 server->client MAC algorithm
! 2005-03-14 16:48:25.137 Using username "keyur".
. 2005-03-14 16:48:25.147 Keyboard-interactive authentication refused
. 2005-03-14 16:48:25.147 Session password prompt (keyur@192.168.10.57's
password: )
. 2005-03-14 16:48:25.147 Using stored password.
. 2005-03-14 16:48:25.147 Sent password
! 2005-03-14 16:48:27.501 Access denied
. 2005-03-14 16:48:27.501 Access denied
. 2005-03-14 16:48:27.501 Session password prompt (keyur@192.168.10.57's
password: )
. 2005-03-14 16:48:27.501 Asking user for password.
. 2005-03-14 16:48:28.462 Sent password
! 2005-03-14 16:48:30.816 Access denied
. 2005-03-14 16:48:30.816 Access denied
. 2005-03-14 16:48:30.816 Session password prompt (keyur@192.168.10.57's
password: )
. 2005-03-14 16:48:30.816 Asking user for password.
. 2005-03-14 16:48:31.527 Unable to authenticate
. 2005-03-14 16:48:31.527 Attempt to close connection due to fatal
exception:
* 2005-03-14 16:48:31.527 Unable to authenticate
. 2005-03-14 16:48:31.527 Closing connection.
* 2005-03-14 16:48:31.537 (ESshFatal) Authentication failed.
* 2005-03-14 16:48:31.537 Authentication log (see session log for details):
* 2005-03-14 16:48:31.537 Using username "keyur".
* 2005-03-14 16:48:31.537 Access denied
* 2005-03-14 16:48:31.537 Access denied
* 2005-03-14 16:48:31.537 
* 2005-03-14 16:48:31.537 Unable to authenticate

WORKING
--------------

. 2005-03-14 16:52:19.965
--------------------------------------------------------------------------
. 2005-03-14 16:52:20.005 WinSCP Version 3.7.3 (Build 265) (OS 5.0.2195
Service Pack 4)
. 2005-03-14 16:52:20.005 Login time: Monday, March 14, 2005 4:52:20 PM
. 2005-03-14 16:52:20.005
--------------------------------------------------------------------------
. 2005-03-14 16:52:20.005 Session name: gagan@local
. 2005-03-14 16:52:20.005 Host name: 192.168.10.57 (Port: 22)
. 2005-03-14 16:52:20.005 User name: gagan (Password: Yes, Key file: No)
. 2005-03-14 16:52:20.005 Transfer Protocol: SFTP (SCP)
. 2005-03-14 16:52:20.005 SSH protocol version: 2; Compression: No
. 2005-03-14 16:52:20.005 Agent forwarding: No; TIS/CryptoCard: No; KI: Yes;
GSSAPI: No
. 2005-03-14 16:52:20.005 Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. 2005-03-14 16:52:20.005 Ping type: -, Ping interval: 30 sec; Timeout: 15
sec
. 2005-03-14 16:52:20.005 SSH Bugs: -,-,-,-,-,-,-,-
. 2005-03-14 16:52:20.005 SFTP Bugs: -,-
. 2005-03-14 16:52:20.005 Proxy: none
. 2005-03-14 16:52:20.005 Return code variable: Autodetect; Lookup user
groups: Yes
. 2005-03-14 16:52:20.005 Shell: default, EOL: 0
. 2005-03-14 16:52:20.005 Local directory: default, Remote directory: home,
Update: No, Cache: Yes
. 2005-03-14 16:52:20.005 Cache directory changes: Yes, Permanent: Yes
. 2005-03-14 16:52:20.005 Clear aliases: Yes, Unset nat.vars: Yes, Resolve
symlinks: Yes
. 2005-03-14 16:52:20.005 Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. 2005-03-14 16:52:20.005
--------------------------------------------------------------------------
. 2005-03-14 16:52:20.005 Looking up host "192.168.10.57"
. 2005-03-14 16:52:20.005 Connecting to 192.168.10.57 port 22
. 2005-03-14 16:52:20.055 Server version: SSH-1.99-OpenSSH_3.5p1
. 2005-03-14 16:52:20.055 We claim version: SSH-2.0-WinSCP_release_3.7.3
. 2005-03-14 16:52:20.055 Using SSH protocol version 2
. 2005-03-14 16:52:20.055 Doing Diffie-Hellman group exchange
. 2005-03-14 16:52:20.105 Doing Diffie-Hellman key exchange
. 2005-03-14 16:52:22.979 Host key fingerprint is:
. 2005-03-14 16:52:22.979 ssh-rsa 1024
70:ea:61:3a:cb:96:f9:02:3b:99:4f:81:da:93:a1:06
. 2005-03-14 16:52:22.979 Initialised AES-256 client->server encryption
. 2005-03-14 16:52:22.979 Initialised HMAC-SHA1 client->server MAC algorithm
. 2005-03-14 16:52:22.989 Initialised AES-256 server->client encryption
. 2005-03-14 16:52:22.989 Initialised HMAC-SHA1 server->client MAC algorithm
! 2005-03-14 16:52:22.989 Using username "gagan".
. 2005-03-14 16:52:22.999 Keyboard-interactive authentication refused
. 2005-03-14 16:52:22.999 Session password prompt (gagan@192.168.10.57's
password: )
. 2005-03-14 16:52:22.999 Using stored password.
. 2005-03-14 16:52:22.999 Sent password
. 2005-03-14 16:52:23.009 Access granted
. 2005-03-14 16:52:23.009 Opened channel for session
. 2005-03-14 16:52:23.029 Started a shell/command
. 2005-03-14 16:52:23.029
--------------------------------------------------------------------------
. 2005-03-14 16:52:23.029 Using SFTP protocol.
. 2005-03-14 16:52:23.029 Doing startup conversation with host.
> 2005-03-14 16:52:23.029 Type: SSH_FXP_INIT, Size: 5, Number: -1
< 2005-03-14 16:52:23.029 Type: SSH_FXP_VERSION, Size: 5, Number: -1
. 2005-03-14 16:52:23.029 SFTP version 3 negotiated.
> 2005-03-14 16:52:23.029 Type: SSH_FXP_EXTENDED, Size: 38, Number: 200
< 2005-03-14 16:52:23.029 Type: SSH_FXP_STATUS, Size: 38, Number: 200
< 2005-03-14 16:52:23.029 Status/error code: 8
. 2005-03-14 16:52:23.029 Server does not recognise WinSCP.
. 2005-03-14 16:52:23.039 Getting current directory name.
. 2005-03-14 16:52:23.039 Getting real path for '.'
> 2005-03-14 16:52:23.039 Type: SSH_FXP_REALPATH, Size: 10, Number: 528
< 2005-03-14 16:52:23.039 Type: SSH_FXP_NAME, Size: 43, Number: 528
. 2005-03-14 16:52:23.039 Real path is '/home/gagan'
. 2005-03-14 16:52:23.039 Listing directory "/home/gagan".
> 2005-03-14 16:52:23.039 Type: SSH_FXP_OPENDIR, Size: 20, Number: 779
< 2005-03-14 16:52:23.039 Type: SSH_FXP_HANDLE, Size: 13, Number: 779
> 2005-03-14 16:52:23.039 Type: SSH_FXP_READDIR, Size: 13, Number: 1036
< 2005-03-14 16:52:23.049 Type: SSH_FXP_NAME, Size: 783, Number: 1036
> 2005-03-14 16:52:23.049 Type: SSH_FXP_READDIR, Size: 13, Number: 1292
. 2005-03-14 16:52:23.049 Reading symlink "marketing".
> 2005-03-14 16:52:23.049 Type: SSH_FXP_READLINK, Size: 30, Number: 1555
> 2005-03-14 16:52:23.049 Type: SSH_FXP_STAT, Size: 30, Number: 1809
< 2005-03-14 16:52:23.049 Type: SSH_FXP_STATUS, Size: 28, Number: 1292
. 2005-03-14 16:52:23.049 Storing reserved response
< 2005-03-14 16:52:23.059 Type: SSH_FXP_NAME, Size: 65, Number: 1555
< 2005-03-14 16:52:23.180 Type: SSH_FXP_ATTRS, Size: 37, Number: 1809
. 2005-03-14 16:52:23.180 Reading symlink "public".
> 2005-03-14 16:52:23.180 Type: SSH_FXP_READLINK, Size: 27, Number: 2067
> 2005-03-14 16:52:23.180 Type: SSH_FXP_STAT, Size: 27, Number: 2321
< 2005-03-14 16:52:23.190 Type: SSH_FXP_NAME, Size: 59, Number: 2067
< 2005-03-14 16:52:23.190 Type: SSH_FXP_ATTRS, Size: 37, Number: 2321
. 2005-03-14 16:52:23.190 Reading symlink "wowerpresumes".
> 2005-03-14 16:52:23.190 Type: SSH_FXP_READLINK, Size: 34, Number: 2579
> 2005-03-14 16:52:23.190 Type: SSH_FXP_STAT, Size: 34, Number: 2833
< 2005-03-14 16:52:23.190 Type: SSH_FXP_NAME, Size: 73, Number: 2579
< 2005-03-14 16:52:23.200 Type: SSH_FXP_ATTRS, Size: 37, Number: 2833
. 2005-03-14 16:52:23.200 Reading symlink "wow_resumes".
> 2005-03-14 16:52:23.200 Type: SSH_FXP_READLINK, Size: 32, Number: 3091
> 2005-03-14 16:52:23.200 Type: SSH_FXP_STAT, Size: 32, Number: 3345
< 2005-03-14 16:52:23.200 Type: SSH_FXP_NAME, Size: 69, Number: 3091
< 2005-03-14 16:52:23.200 Type: SSH_FXP_ATTRS, Size: 37, Number: 3345
. 2005-03-14 16:52:23.200 Reading symlink "technical".
> 2005-03-14 16:52:23.200 Type: SSH_FXP_READLINK, Size: 30, Number: 3603
> 2005-03-14 16:52:23.200 Type: SSH_FXP_STAT, Size: 30, Number: 3857
< 2005-03-14 16:52:23.210 Type: SSH_FXP_NAME, Size: 65, Number: 3603
< 2005-03-14 16:52:23.210 Type: SSH_FXP_ATTRS, Size: 37, Number: 3857
< 2005-03-14 16:52:23.210 Status/error code: 1
> 2005-03-14 16:52:23.210 Type: SSH_FXP_CLOSE, Size: 13, Number: 4100
. 2005-03-14 16:52:23.210 Startup conversation with host finished.
. 2005-03-14 16:52:26.304 Closing connection.

-
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

SOLVED: Some users locked out of ssh and sftp?

[Eve Atley]

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.

- Eve


-
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

Re: SOLVED: Some users locked out of ssh and sftp?

[Ray Olszewski]

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 on 
this, at the least.

.Xauthority should have no connection with ssh logins ... and I just 
verified that the one host where I have an account but no .Xauthority file 
(this file derives from running X sessions, as you might guess from the 
name, so is present on my workstations) connects just fine with Winscp.

I don't know what "user account is locked"  means, possibly hecause I don't 
know the context in which you got that message.


-
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

RE: SOLVED: Some users locked out of ssh and sftp?

[Eve Atley]

>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 included is a simple checkbox: "User account is
locked." On a whim, I unchecked this and things started working for me.

Which seems somehow too simple...

- Eve


-
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