Does anybody mind if I change the pam_opie(8) prompt from Password:
to Response:? I think users might be slightly confused when they
enter an incorrect or empty response twice and get a new Password:
prompt and don't realize it's the pam_unix(8) prompt.
DES
--
Dag-Erling Smorgrav - [EMAIL
On Mon, Jan 21, 2002 at 03:18:32PM +0100, Dag-Erling Smorgrav wrote:
Does anybody mind if I change the pam_opie(8) prompt from Password:
to Response:? I think users might be slightly confused when they
enter an incorrect or empty response twice and get a new Password:
prompt and don't
On Mon, Jan 21, 2002 at 15:18:32 +0100, Dag-Erling Smorgrav wrote:
Does anybody mind if I change the pam_opie(8) prompt from Password:
to Response:? I think users might be slightly confused when they
enter an incorrect or empty response twice and get a new Password:
prompt and don't realize
Does anybody mind if I change the pam_opie(8) prompt from Password:
to Response:? I think users might be slightly confused when they
enter an incorrect or empty response twice and get a new Password:
prompt and don't realize it's the pam_unix(8) prompt.
Nope - that sounds good!
M
--
o
On Mon, Jan 21, 2002 at 17:29:01 +0300, Andrey A. Chernov wrote:
enter an incorrect or empty response twice and get a new Password:
prompt and don't realize it's the pam_unix(8) prompt.
Wait... First of all, there (I mean original OPIE) must be 2 prompts in
worst case, not 3 prompts:
I
Andrey A. Chernov [EMAIL PROTECTED] writes:
On Mon, Jan 21, 2002 at 15:18:32 +0100, Dag-Erling Smorgrav wrote:
Does anybody mind if I change the pam_opie(8) prompt from Password:
to Response:? I think users might be slightly confused when they
enter an incorrect or empty response twice
Andrey A. Chernov [EMAIL PROTECTED] writes:
I can't reproduce your 3 prompts situation (or may I misread what you try
to say?) I got only 2 prompts in login and su.
des@des ~% login des
otp-md5 496 de6973 ext
Password: enter
otp-md5 496 de6973 ext
Password [echo on]: enter
Password: unix
On Mon, Jan 21, 2002 at 16:13:54 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
I can't reproduce your 3 prompts situation (or may I misread what you try
to say?) I got only 2 prompts in login and su.
des@des ~% login des
otp-md5 496 de6973 ext
Password:
On Mon, Jan 21, 2002 at 16:11:47 +0100, Dag-Erling Smorgrav wrote:
Back to your subj.: It breaks, at least, M$ Windows OPIE/Skey generators
which do auto-paste when keyword (Password) is found.
Good point. OPIE Password might be more appropriate, then.
We don't know, what exact
Andrey A. Chernov [EMAIL PROTECTED] writes:
Yes, I see it too now. It is definitely some bug here. When I say in
login I mean I test it through:
The bug is quite simply that pam_opie(8) never sets the AUTHTOK item,
so pam_unix(8) doesn't know that the user already entered a password.
I
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
The bug is quite simply that pam_opie(8) never sets the AUTHTOK item,
so pam_unix(8) doesn't know that the user already entered a password.
I believe pam_get_pass() should set PAM_AUTHTOK. Any objections?
OK, now I'm really off my rocker;
Andrey A. Chernov [EMAIL PROTECTED] writes:
Yes, I see it too now. It is definitely some bug here. When I say in
login I mean I test it through:
The bug is quite simply that pam_opie(8) never sets the AUTHTOK item,
so pam_unix(8) doesn't know that the user already entered a password.
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
OK, now I'm really off my rocker; pam_conv_pass() (called by
pam_get_pass()) does set PAM_AUTHTOK. I still don't understand why
it's NULL by the time pam_unix(8) calls pam_get_pass(). I'll
investigate further.
I found the bug: login(1) only
On Mon, Jan 21, 2002 at 16:45:41 +0100, Dag-Erling Smorgrav wrote:
The bug is quite simply that pam_opie(8) never sets the AUTHTOK item,
so pam_unix(8) doesn't know that the user already entered a password.
I believe pam_get_pass() should set PAM_AUTHTOK. Any objections?
No objections.
--
On Mon, Jan 21, 2002 at 17:14:24 +0100, Dag-Erling Smorgrav wrote:
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
OK, now I'm really off my rocker; pam_conv_pass() (called by
pam_get_pass()) does set PAM_AUTHTOK. I still don't understand why
it's NULL by the time pam_unix(8) calls
On Mon, Jan 21, 2002 at 18:32:43 +0300, Andrey A. Chernov wrote:
On Mon, Jan 21, 2002 at 16:11:47 +0100, Dag-Erling Smorgrav wrote:
Back to your subj.: It breaks, at least, M$ Windows OPIE/Skey generators
which do auto-paste when keyword (Password) is found.
Good point. OPIE
Andrey A. Chernov [EMAIL PROTECTED] writes:
it gives impression that no normal Unix password can be typed at this
point.
...which I initially thought was the case, but it's not.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Dag-Erling Smorgrav wrote:
Does anybody mind if I change the pam_opie(8) prompt from Password:
to Response:? I think users might be slightly confused when they
enter an incorrect or empty response twice and get a new Password:
prompt and don't realize it's the pam_unix(8) prompt.
See my
Ruslan Ermilov wrote:
On Mon, Jan 21, 2002 at 03:18:32PM +0100, Dag-Erling Smorgrav wrote:
Does anybody mind if I change the pam_opie(8) prompt from Password:
to Response:? I think users might be slightly confused when they
enter an incorrect or empty response twice and get a new Password
19 matches
Mail list logo
