Bug 77777 - second root login (with rlogin) attempt fails
second root login (with rlogin) attempt fails
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: pam (Show other bugs)
7.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-13 09:10 EST by Andreas Luik
Modified: 2015-01-07 19:01 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-13 05:33:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andreas Luik 2002-11-13 09:10:51 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; SunOS 5.8 sun4u)

Description of problem:
I have enabled root logins by adding "rlogin" to /etc/securetty.
If I use the correct password initially, the login works.
But if I use an incorrect root-password at the first attempt, all
further attempts fail with "Login incorrect", even if I use the
correct password:

pascal% rlogin mg -l root
Password: <incorrect password>
Password: <correct password>
Login incorrect

login: root
Password: <correct password>
Login incorrect



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Add "rlogin" to /etc/securetty on machine A.
2. On machine B, "rlogin A -l root"
3. Enter wrong password initially.
4. Enter correct password at the second "Password:" prompt.
	

Actual Results:  Login incorrect


Additional info:
Comment 1 Tomas Mraz 2004-11-09 10:26:18 EST
Please retest with latest Fedora Core distribution.
Comment 2 Andreas Luik 2004-12-09 05:24:43 EST
I will, as soon as we have FC 3 installed.
Comment 3 Tomas Mraz 2005-01-13 05:33:24 EST
Reopen if still apears.

Note You need to log in before you can comment on or make changes to this bug.