Re: SRA login failed -- bug?

2002-05-20 Thread Archie Cobbs

Marcel Moolenaar writes:
> > I see this as well - on both -STABLE and -CURRENT. I do you have two
> > accounts you can try? I generally find that while the SRA login will
> > refuse one account, a different account can log in fine, without
> > reconnecting the telnet.
> 
> Ok, now that I have confirmation, I'll see if I can zoom in on the
> problem. Does anybody have a informed opinion as to where to start:
> server or client?

I haven't seen this for a while because I started using ssh exclusively
a while back -- so this info may be out of date...  but when I did
see it, ISTR that there was often an error message on the server..

-Archie

__
Archie Cobbs * Packet Design * http://www.packetdesign.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SRA login failed -- bug?

2002-05-20 Thread Marcel Moolenaar

On Mon, May 20, 2002 at 09:35:31AM +0100, Gavin Atkinson wrote:
> 
> I see this as well - on both -STABLE and -CURRENT. I do you have two
> accounts you can try? I generally find that while the SRA login will
> refuse one account, a different account can log in fine, without
> reconnecting the telnet.

I have multiple accounts, but have not tried to login with another
user while the first "locks". For some reason I never saw a reason to
think it had a more global effect.  And yes, I do see it on -stable
as well (forgot to mention).

Ok, now that I have confirmation, I'll see if I can zoom in on the
problem. Does anybody have a informed opinion as to where to start:
server or client?

-- 
 Marcel Moolenaar USPA: A-39004  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SRA login failed -- bug?

2002-05-20 Thread John Polstra

In article <[EMAIL PROTECTED]>,
Marcel Moolenaar  <[EMAIL PROTECTED]> wrote:
> I sometimes cannot get passed SRA secure login, even though credentials
> are given correctly:
> 
> Connected to athlon.pn.xcllnt.net.
> Escape character is '^]'.
> Trying SRA secure login:
> User (marcel): 
> Password: 
> [ SRA login failed ]
>   :
>   (repeat last 3 lines -- Ad nauseam)
> 
> The problem is not a faulty password or username, but appears to be
> something that behaves much the same as uninitialized variables.
> Most of the time SRA secure login works ok, but it does occasionally
> reject the login. It is not possible to login at all when SRA rejects
> a login. It's a permanent state and the only way around it is to
> ^C and re-telnet, which BTW occasionally fails as well...
> 
> I haven't seen anything on this topic, so I'd like to hear if
> others are experiencing this as well and if this is a security
> "feature", a bug or misconfiguration.

Yes, I see this sometimes too, even in -stable.  I agree with your
conjecture -- it acts like there's an uninitialized variable that
sometimes starts out with an unworkable value.

John
-- 
  John Polstra
  John D. Polstra & Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SRA login failed -- bug?

2002-05-20 Thread Gavin Atkinson

On Sun, 19 May 2002, Marcel Moolenaar wrote:
> I sometimes cannot get passed SRA secure login, even though credentials
> are given correctly:
>
> Connected to athlon.pn.xcllnt.net.
> Escape character is '^]'.
> Trying SRA secure login:
> User (marcel):
> Password:
> [ SRA login failed ]
>   :
>   (repeat last 3 lines -- Ad nauseam)
>
> I haven't seen anything on this topic, so I'd like to hear if
> others are experiencing this as well and if this is a security
> "feature", a bug or misconfiguration.

I see this as well - on both -STABLE and -CURRENT. I do you have two
accounts you can try? I generally find that while the SRA login will
refuse one account, a different account can log in fine, without
reconnecting the telnet.

I'm glad someone else has seen this, i thought i was going mad...

Gavin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message