While doing updates on my servers, I came across this one and I'm
baffled. I always ssh into my primary server and then ssh to the
others. I have them all setup to use keys, and normally it just logs in
and records this in syslog. However, after rpm updated
openssh/openssh-clients/openssh
On Tue, 2003-08-05 at 06:54, Michael Schwendt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, 04 Aug 2003 22:22:16 -0600, Ashley M. Kirchner wrote:
>
> > While doing updates on my servers, I came across this one and I'm
> > baffled. I always ssh into my primary server a
On Thu, 2003-08-07 at 21:09, Bret Hughes wrote:
> On Tue, 2003-08-05 at 06:54, Michael Schwendt wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Mon, 04 Aug 2003 22:22:16 -0600, Ashley M. Kirchner wrote:
> >
> > > While doing updates on my servers, I came across this on
RedHat really introduced one more bug.
When authenting through kerberos (pam_krb5), redhat's sshd will segfault.
There are a couple of bug reports of this in bugzilla, but no coments from
redhat so far.
I do not understand why the login process should take longer time than usual.
The security
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07 Aug 2003 21:09:45 -0500, Bret Hughes wrote:
> > See clarifying comment at end of
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=101157
> >
>
> I assume that you are referring to:
>
>
> If the only solution to the information leak i
RedHat really introduced one more bug.
When authenting through kerberos (pam_krb5), redhat's sshd will segfault.
There are a couple of bug reports of this in bugzilla, but no coments
from redhat so far.
I do not understand why the login process should take longer time than
usual.
The security i
On Tue, 2003-08-05 at 07:22, Ashley M. Kirchner wrote:
> Notice how pam now says it failed authentication, yet it logged me
> in. Um, what's going on?
It seems to be a problem with the ssh package. I remember someone else
complaining about this, and I experience it too on both RH72 and RH73
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 04 Aug 2003 22:22:16 -0600, Ashley M. Kirchner wrote:
> While doing updates on my servers, I came across this one and I'm
> baffled. I always ssh into my primary server and then ssh to the
> others. I have them all setup to use keys, a
