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 ([EMAIL PROTECTED]) as well as a
working
session ([EMAIL PROTECTED]).
NON-WORKING
I have to think about the message in general, but I wanted to correct one
small error in your procedure right away.
At 02:17 PM 3/14/2005 -0500, Eve Atley wrote:
[...]
So I tried copying one of these known_hosts to /home/keyur/.ssh/known_hosts.
When I next try a locate for known_hosts, keyur neve
As a side note, it as if most of the 'older' users can login, but the newer
users cannot! I just tried with another user...michele, who was one of the
earliest users but has previously never logged in via SSH...and she had no
issues whatsoever.
- Eve
-
To unsubscribe from this list: send the lin
>>OK. Now though you call it a "session" password, this is just the same
>>password that the user has already entered in as "password1" (from below).
>>Right?
In this case, they should be able to log in as, say, jean/password1, as you
say. This is entered in the winscp fields, ie. testing local
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 c
Eve Emshoff wrote:
> Thus far, I've run across 1 user who can't sftp OR
> SSH. He's entirely locked out, despite having the
> correct username and password. He appears to be set up
> the same as well the others.
>
> Is there a file or some such I should edit and/or
> check to ensure he can get ac
Yeah, Eve, details help a lot. My memory of your earlier postings on this
is a bit hazy, so I may be dragging you through something you've already
tried. If so, I'm sorry. But based on the fresh info, I have a couple of
suggestions, provided below.
At 05:56 PM 3/11/2005 -0500, Eve Atley wrote:
Had the same problem. My problem was solved when I install all the packages
required for log in in all the computers. Suggest you check upor packages.
PS All packages REQUIRED for login DO NOT have SSH as part of their name.
Sorry can not remember what the additional names are.
Frank
On Friday
Ok, let me see if I can narrow the problem down a bit. Using the GUI panel,
I first create a user and password combination - let's use jean / password1.
This autocreates a user home directory (jean) and gives them a bash shell
(in this case).
Then, via terminal, I 'useradd jean'. Following this,
On Tuesday 01 March 2005 10:59 am, Ray Olszewski wrote:
> At 08:22 AM 3/1/2005 -0800, Eve Emshoff wrote:
> >This isn't making sense to me. I have users logging in
> >via SSH to a redhat linux box using their network
> >username/password. I'm able to do it as are most
> >others, either locally or re
At 08:22 AM 3/1/2005 -0800, Eve Emshoff wrote:
This isn't making sense to me. I have users logging in
via SSH to a redhat linux box using their network
username/password. I'm able to do it as are most
others, either locally or remotely. ie:
ssh -l eve
or
sftp eve@
Thus far, I've run across 1 user
11 matches
Mail list logo
