From: "Eve Atley" <eatley@wowcorp.com>
To: 'Ray Olszewski' <ray@comarre.com>, linux-newbie@vger.kernel.org
Subject: RE: Some users locked out of ssh and sftp?
Date: Mon, 14 Mar 2005 14:17:24 -0500 [thread overview]
Message-ID: <00b801c528ca$745576b0$4f0aa8c0@lanadmin> (raw)
In-Reply-To: <5.1.0.14.1.20050311152407.01f6ecc0@celine>
>>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 locally:
Host name: 192.168.10.57
Port number: 22
User name: jean
Password: password1
> ... if I enter the correct password in the password box, then it
>logs me on without any fuss.
Yeah, that's how it *should* work. :)
> ... if I enter the wrong password in the password box, then it
>prompts me for a password (probably what you call the "session" password).
Still prompts me, no matter what I enter, right or wrong. I have reset the
password on jean several times from the Linux box; then tried reentering the
password each time and it still prompts me and denies jean access.
>Second, still in Winscp3, check in Advanced Options->Authentication and
>make sure "Attempt keyboard-active authentication" and "Respond with
>password to the first prompt" are both checked.
Checked.
>Third, still in Winscp3, check in SSH to make sure SSH2 is the only, or at
>least the preferred, connection method.
Done.
>Last, I've assumed we are in all cases talking about connecting to the same
>server. You certainly seem to be saying that. But if I've misunderstood
>you ... might there be differences in the sshd implementations between
>servers that do and do not prompt for the password? This could be an SSH1
>versus SSH2 issue, for example.
My test environment is simply this. I try connecting to a variety of users
from my own machine, to the same machine in all cases. So, whereas
credentials for 'eve' work, credentials for 'jean' do not. So it's not a
client setup issue that I can see...quite possibly the way the user is set
up, though how so I can't place.
Now, I wondered if the known_hosts problem may clue me into something, but
here's my return when I locate known_hosts:
/root/.ssh/known_hosts
/home/kolt/.ssh/known_hosts
/home/eve/.ssh/known_hosts
/home/edwin/.ssh/known_hosts
/home/navneet/.ssh/known_hosts
/home/vaibhav/.ssh/known_hosts
This translates to: eve can log in as well as all the others shown
here...but so can Gagan, who has no such known_hosts file.
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 never actually appears in
the listing.
/root/.ssh/known_hosts
/home/kolt/.ssh/known_hosts
/home/eve/.ssh/known_hosts
/home/edwin/.ssh/known_hosts
/home/navneet/.ssh/known_hosts
/home/vaibhav/.ssh/known_hosts
...even when ensuring permissions are set the same as Gagan.
- 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
next prev parent reply other threads:[~2005-03-14 19:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 5:50 Sype wont't open Peter H.
2005-03-01 6:21 ` Ray Olszewski
2005-03-01 7:10 ` Richard Adams
2005-03-01 7:13 ` Skype " Peter
2005-03-01 16:22 ` Some users locked out of ssh and sftp? Eve Emshoff
2005-03-01 16:59 ` Ray Olszewski
2005-03-02 1:26 ` Eric Bambach
2005-03-11 19:20 ` Thought I was mounting drive correctly, but backup failed Eve Atley
2005-03-11 21:37 ` Ray Olszewski
2005-03-11 22:35 ` Eve Atley
2005-03-11 22:54 ` Ray Olszewski
2005-03-11 23:49 ` Eve Atley
2005-03-11 22:56 ` Some users locked out of ssh and sftp? Eve Atley
2005-03-11 23:27 ` SOTL
2005-03-13 23:44 ` SOTL
2005-03-12 0:15 ` Ray Olszewski
2005-03-14 19:17 ` Eve Atley [this message]
2005-03-14 19:45 ` Ray Olszewski
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
2005-03-14 19:20 ` Eve Atley
2005-03-12 1:06 ` Marcus Furlong
2005-03-01 6:58 ` Sype wont't open Richard Adams
2005-03-01 8:17 ` Skype " Peter
2005-03-02 2:07 ` Peter
2005-03-02 3:00 ` Ray Olszewski
2005-03-02 5:53 ` Peter
2005-03-02 6:51 ` Richard Adams
2005-03-02 7:33 ` Peter
2005-03-03 6:34 ` Richard Adams
2005-03-03 9:56 ` Peter
2005-03-03 11:25 ` chuck gelm
2005-03-03 16:37 ` Richard Adams
2005-03-01 9:46 ` Sype " chuck gelm
2005-03-01 14:18 ` Richard Adams
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='00b801c528ca$745576b0$4f0aa8c0@lanadmin' \
--to=eatley@wowcorp.com \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.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