Bug 101662 - Openssh errata causes login delay
Summary: Openssh errata causes login delay
Keywords:
Status: CLOSED DUPLICATE of bug 101157
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: openssh
Version: 7.3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-05 12:10 UTC by Kevin M. Myer
Modified: 2007-04-18 16:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:57:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Kevin M. Myer 2003-08-05 12:10:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
After upgrading to the latest openssh eratta, there is a noticeable delay in
logging into remote systems.  I also noticed a marked rise in failed login
attempts and found a one-to-one correlation between each login and each failed
login.  Apparently what is happening is each successful login attempt is first
generating a failed attempt, and then the login occurs successfully.

So far I can confirm that this affects Red Hat 7.3, 9.0 and AS 2.1, using both
password and publickey and using straight files or LDAP for authentication. 
Since the errata was to fix an issue with timing and PAM, it seems highly likely
that the fix is a bit overzealous.

Version-Release number of selected component (if applicable):
openssh-3.1p1-8

How reproducible:
Always

Steps to Reproduce:
1.Login to server
2.wait a few seconds
3.review log and see failed login
    

Actual Results:  Same as above

Expected Results:  Speedy login and no login failure logged.

Additional info:

Comment 1 Kevin M. Myer 2003-08-07 14:47:58 UTC
My bad - I somehow missed all the other filings of this bug.. mustn't drank my
coffee yet

*** This bug has been marked as a duplicate of 101157 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:57:59 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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