On Tue, 2003-09-09 at 01:09, Gordon Messmer wrote:
> lists wrote:
> > One work around that I have found is to comment out the first line in
> > the sshd pam configuration.
> >
> > #%PAM-1.0
> > #auth required pam_stack.so service=system-auth
> > auth required pam_nologin.so
>
lists wrote:
One work around that I have found is to comment out the first line in
the sshd pam configuration.
#%PAM-1.0
#auth required pam_stack.so service=system-auth
auth required pam_nologin.so
accountrequired pam_stack.so service=system-auth
password required
Meant to send this to the list :
Be interesting to see what forwarding does to the threading.
On Fri, 2003-09-05 at 18:09, Sean Estabrooks wrote:
> On 05 Sep 2003 17:58:37 -0500
> Bret Hughes <[EMAIL PROTECTED]> wrote:
>
>
> > I don't know what the recourse would be if I were to really raise h
Sean Estabrooks wrote:
On Fri, 05 Sep 2003 19:05:24 -0400
lists <[EMAIL PROTECTED]> wrote:
One work around that I have found is to comment out the first line in
the sshd pam configuration.
#%PAM-1.0
#auth required pam_stack.so service=system-auth
auth required pam_nologi
On Fri, 2003-09-05 at 15:39, Benjamin J. Weiss wrote:
> No, it pisses me off, as well. I just haven't had the time to complain to
> RedHat that they've royally messed up all of my logs. I'm also hoping and
> praying that RH 10 will fix this problem...
Me as well. When these frigging "NON BUGS
On Fri, 05 Sep 2003 19:05:24 -0400
lists <[EMAIL PROTECTED]> wrote:
> One work around that I have found is to comment out the first line in
> the sshd pam configuration.
>
> #%PAM-1.0
> #auth required pam_stack.so service=system-auth
> auth required pam_nologin.so
> account
On 05 Sep 2003 17:58:37 -0500
Bret Hughes <[EMAIL PROTECTED]> wrote:
> I don't know what the recourse would be if I were to really raise hell.
> It appears that the maintainer of RH packages has the power to declare
> issues NOTABUG and I do not know the procedure to go over them.
>
> I pleaded
One work around that I have found is to comment out the first line in
the sshd pam configuration.
#%PAM-1.0
#auth required pam_stack.so service=system-auth
auth required pam_nologin.so
accountrequired pam_stack.so service=system-auth
password required pam_stack.s
Ignore the previous post. The system ignores it..
Benjamin J. Weiss wrote:
Following are two entries from our /var/log/messages file and I'm
wondering about the 'authentication failure' part. This seems to
happen with every login, at least remote, although the user logs in
normally with n
On Fri, 2003-09-05 at 16:51, Sean Estabrooks wrote:
> On 05 Sep 2003 16:30:03 -0500
> Bret Hughes <[EMAIL PROTECTED]> wrote:
>
> > On Fri, 2003-09-05 at 13:10, Peter Fleck wrote:
> > > Hi,
> > >
> > > Following are two entries from our /var/log/messages file and I'm
> > > wondering about the 'au
To fix the logging crap change your /etc/ssh/sshd_config to match this.
# Logging
#obsoletes QuietMode and FascistLogging
SyslogFacility AUTH
#SyslogFacility AUTHPRIV
#LogLevel INFO
Comment AUTHPRIV and uncomment AUTH for the SyslogFacility.
Benjamin J. Weiss wrote:
Following are two entries fro
> > Following are two entries from our /var/log/messages file and I'm
> > wondering about the 'authentication failure' part. This seems to
> > happen with every login, at least remote, although the user logs in
> > normally with no problem. Can we change some setting to make this go
> > away?
>
On 05 Sep 2003 16:30:03 -0500
Bret Hughes <[EMAIL PROTECTED]> wrote:
> On Fri, 2003-09-05 at 13:10, Peter Fleck wrote:
> > Hi,
> >
> > Following are two entries from our /var/log/messages file and I'm
> > wondering about the 'authentication failure' part. This seems to
> > happen with every log
On Fri, 2003-09-05 at 13:10, Peter Fleck wrote:
> Hi,
>
> Following are two entries from our /var/log/messages file and I'm
> wondering about the 'authentication failure' part. This seems to
> happen with every login, at least remote, although the user logs in
> normally with no problem. Can we
Hi,
Following are two entries from our /var/log/messages file and I'm
wondering about the 'authentication failure' part. This seems to
happen with every login, at least remote, although the user logs in
normally with no problem. Can we change some setting to make this go
away?
Thanks.
Sep 3
15 matches
Mail list logo