-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Quinson schrieb:
Filling a bug at severity critical without a single word in the message
body
sounds like a bad joke for me.
It is not a joke.
Ok. Let's say I was overreacting to the cruel lack of information of your
initial bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Perrier schrieb:
There may have been some overreacting because indeed noone really
likes to receive RC bugs for a key package very few days before a
release. Martin, please accept our apologies ifsome words have been
too rude.
I
su falls on me vserver if pam_login is set to required.
I set it to optional, and now su works fine.
Strange, but I thing its no longer a debian bug.
I thing I must kick my hoster in the ass.
In name of shadow maintainers, thanks to your involvment tracking down
this issue. Thanks as well to
severity 310185 important
tags 310185 unreproducible
thanks
Quoting Martin Wodrich ([EMAIL PROTECTED]):
Package: login
Version: 1:4.0.3-31sarge5
Severity: critical
Justification: breaks the whole system
I see absolutely no reason for a non working su to break whole
system.
An, I absolutely
On Sun, May 22, 2005 at 02:02:28PM +0200, Christian Perrier wrote:
severity 310185 important
tags 310185 unreproducible
thanks
Quoting Martin Wodrich ([EMAIL PROTECTED]):
Package: login
Version: 1:4.0.3-31sarge5
Severity: critical
Justification: breaks the whole system
I see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin,
I can't reproduce this on sarge/i386. Please could you make sure your
system is fully up-to-date, and then try again. Also, please post a
transcript of the commands, so we can see exactly how to reproduce it.
Thanks,
Roger
- --
Roger
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Leigh schrieb:
I can't reproduce this on sarge/i386. Please could you make sure your
system is fully up-to-date,
My system is fully up-to-date. But it is not a real server. Its a
vserver from Vollmar.net ( http://www.vlinux.de)
and then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Quinson schrieb:
Filling a bug at severity critical without a single word in the message body
sounds like a bad joke for me.
It is not a joke.
Is it a fresh install?
Its not a fresh install. Its an install of sarge runnig 1,5 years.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Leigh schrieb:
I can't reproduce this on sarge/i386. Please could you make sure your
system is fully up-to-date, and then try again. Also, please post a
transcript of the commands, so we can see exactly how to reproduce it.
The bug can be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Wodrich [EMAIL PROTECTED] writes:
This is my new version (comments removed):
auth sufficient pam_rootok.so
@include common-auth
@include common-account
@include common-session
session optionalpam_limits.so
That looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Leigh schrieb:
This is my new version (comments removed):
auth sufficient pam_rootok.so
@include common-auth
@include common-account
@include common-session
session optionalpam_limits.so
That looks fine.
That the version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Wodrich [EMAIL PROTECTED] writes:
Roger Leigh schrieb:
This is my new version (comments removed):
auth sufficient pam_rootok.so
@include common-auth
@include common-account
@include common-session
session optional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Leigh schrieb:
myself. Befor the fix the last line was:
session requiredpam_limits.so
It wasn't obvious earlier that the problem was pam_limits.so. That
may well be a problem: on my system, I've always made that required,
and it
On Sun, May 22, 2005 at 04:13:31PM +0200, Martin Wodrich wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Quinson schrieb:
Filling a bug at severity critical without a single word in the message body
sounds like a bad joke for me.
It is not a joke.
[...]
Ok. Let's say I
14 matches
Mail list logo
