SOLVED: Some users locked out of ssh and sftp?

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?

[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?

[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

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

Setting quota on user's home folders?

[Eve Atley]

Is there a way to set a quota limit on user's home folders? EG. say I have
/home/joe, /home/jane, and want to set it so they can have no more than 5GB
in their folders?

Thanks,
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: Setting quota on user's home folders?

[J.]

On Wed, 16 Mar 2005, Eve Atley wrote:

> Is there a way to set a quota limit on user's home folders? EG. say I have
> /home/joe, /home/jane, and want to set it so they can have no more than 5GB
> in their folders?
> 
> Thanks,
> Eve

What you have todo is:

1.  Create seperate partitions for the /home/joe /home/jane directory
    entrys.
2.  install the quota program for your native GNU/Linux distribution you
    are using. Which is ??? [Next time tell your system specs when asking 
    a question]
3.  Update /etc/fstab and remount the system.

Note, the kernel has to support the use of quota's in most cases.

Here are some links:
http://www.yolinux.com/TUTORIALS/LinuxTutorialQuotas.html
http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/ch-disk-quotas.html
http://www.eyrie.org/~eagle/notes/debian/quotas.html

B.t.w.
The `Folders' terminology is used in a M$ Wintendo enviroment but in the *X world they 
are refered to as directorys or special files.

cheers

J.

-
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: Setting quota on user's home folders?

[Ray Olszewski]

At 06:43 PM 3/16/2005 -0500, Eve Atley wrote:

>Is there a way to set a quota limit on user's home folders? EG. say I have
>/home/joe, /home/jane, and want to set it so they can have no more than 5GB
>in their folders?

The general answer is yes, and it's called ... wait for it ... quotas. The 
"yes" assumes you are using ext2 filesystems (probably ext3 works too, but 
I don't know that, and maybe other journaling filesystems like reiserfs).

For quotas to work, they have to be enabled in your kernel. Stock kernels 
usually do not include quota capability, so this means a local compile. (If 
you do it with "make menuconfig", quotas are the first choice in the File 
Systems submenu; if you edit .config by hand, you're looking for the line 
"# CONFIG_QUOTA is not set", which you'll change to "CONFIG_QUOTA=y".)

Once you have a kernel that supports quotas, you'll use the "quota" command 
to set actual quotas. Getting this command will probably mean downloading 
an RPM. And there are a few other details that are covered in the link below.

For more background on quotas, look here:

         http://www.asenec.com/quota.html

If all this sounds like too much trouble ... I don't know how comfortable 
you are with custom kernel compiles, say ... you might look for a simpler 
option. Whether some other approach will work depends on what your real 
requirements are.

For example, way back when I admin'd several Unix and Linux systems at a 
school, I just ran this command daily ...

         du -s /home/*  |  sort -nr

... to get a listing that started with the largest home directories. Then I 
told people whose directories were too big to cut back. Not ideal, but it 
was good enough, back in the days when I was sufficiently inexperienced 
that I didn't want to figure out how to enable quotas on Linux 1.something, 
HP-UX, and Solaris.


-
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: Setting quota on user's home folders?

[Peter]

On Wed, 2005-03-16 at 16:31 -0800, Ray Olszewski wrote:
> 
> For quotas to work, they have to be enabled in your kernel. Stock
> kernels 
> usually do not include quota capability, so this means a local
> compile.

I noticed, on running ` locate quota` , that these lines appear in my
output

/lib/modules/2.6.8.1-4-386/kernel/fs/quota_v1.ko
/lib/modules/2.6.8.1-4-386/kernel/fs/quota_v2.ko

I'm thinking this means quotas are supported by modules in this kernel,
and thus a `modprobe quota* ` or similar would suffice, rather than a
kernel recompile.

Is this correct? 

Just thinking this could save Eve and others a *lot* of time...

In Debian, I assume after using the modprobe command the module name
could simply be put in /etc/modules to make loading persistent across
reboots. ( Other distros like the Redhat variants would do this
differently, I suppose)

apt-get install quota

would then install what's necessary for the quota command...



Peter

-
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: Setting quota on user's home folders?

[Eve Atley]

Sorry about not including system info: it's RedHat 9 ATM (to upgrade to RH
Enterprise 3).

>I noticed, on running ` locate quota` , that these lines appear in my
output

I ran this too, and it came back with this:

(truncated)
 /etc/warnquota.conf
/usr/bin/quota
/usr/sbin/edquota
/usr/sbin/quotastats
/usr/sbin/repquota
/usr/sbin/rpc.rquotad
/usr/sbin/setquota
/usr/sbin/warnquota
/sbin/convertquota
/sbin/quotacheck
/sbin/quotaoff
/sbin/quotaon

So, I'm wondering if it's already in my system.

- 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