From owner-freebsd-current Mon May 20 9:58:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id B0D3237C16D for ; Mon, 20 May 2002 09:50:36 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g4KGoYp95185; Mon, 20 May 2002 09:50:34 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g4KGoXQ21981; Mon, 20 May 2002 09:50:33 -0700 (PDT) (envelope-from jdp) Date: Mon, 20 May 2002 09:50:33 -0700 (PDT) Message-Id: <200205201650.g4KGoXQ21981@vashon.polstra.com> To: current@freebsd.org From: John Polstra Cc: marcel@xcllnt.net Subject: Re: SRA login failed -- bug? In-Reply-To: <20020519205152.GA17093@dhcp01.pn.xcllnt.net> References: <20020519205152.GA17093@dhcp01.pn.xcllnt.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020519205152.GA17093@dhcp01.pn.xcllnt.net>, 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) > > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message