If you are using PAM, then it should not be necessary for xscreensaver
to be setuid. Some component of the PAM stack should be setuid
instead (or else PAM can't ever work for non-setuid programs).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
I had this problem too but solved following way.
I think it is not a bug. Some how file mode has been changed.
So, to fix it you should do following.
sudo chmod u+s /usr/X11R6/bin/xscreensaver
That's it.
Good luck.
--
━━……‥‥・・‥‥……━━
Хүндэтгэсэн А.Отгонбаяр
Компаний веб хаяг:
I'm just not going to setuid root xscreensaver, this introduces big
changes of security holes, (see #295526).
Regards,
Jose Luis.
--
ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503
Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org
http://debian.org.ve - irc.debian.org
Solution to this bug is setuid root xscreensaver. Take a look at bug
#295526 -- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295526
It seems that no one is trying to resolve this issue. Would be great
if someone could push unix2_chkpwd solution to Debian as I don't want
to setuid root any
Hi Manuel,
Could you please try with 5.03 version available in sid? I can't since I
don't use PAM...
I just want to know if I can close this bug in the last version ;).
Regards,
Jose Luis.
--
ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503
Weblog: http://ghostbar.ath.cx/ -
Package: xscreensaver
Version: 4.24-1
Severity: important
I have configured my system to use blowfish encrypted passwords, since I
have changed this xscreensaver cannot unlock the screen (authentication
failure).
The configuration for PAM modules in my system is:
[EMAIL PROTECTED]:~$ cat
On Apr 16, 2006, at 10:27 AM, Manuel Lorenzo Frieiro wrote:
I have configured my system to use blowfish encrypted passwords,
since I
have changed this xscreensaver cannot unlock the screen
(authentication
failure).
I have broken my PAM configuration, and so I am reporting a bug
against
Thanks for your answer but I don't think that this error is on my configuration or PAM modules.Other programs (login, wdm, passwd, sudo, su, etc.) work correctly, xscreensaver no.Greetings,Manuel
2006/4/16, Jamie Zawinski [EMAIL PROTECTED]:
On Apr 16, 2006, at 10:27 AM, Manuel Lorenzo Frieiro
Thanks for your answer but I don't think that this error is on my
configuration or PAM modules.
Other programs (login, wdm, passwd, sudo, su, etc.) work correctly,
xscreensaver no.
Did xscreensaver work before you started messing with your PAM
config? Then your PAM config is what broke
Did xscreensaver work before you started messing with your PAM config? Then your PAM config is what broke it.Yes, xscreensaver work ok before. I have changed PAM module pam_unix to pam_unix2 to use blowfish passwords.
In /etc/pam.d/common-auth file I change the original file to the new line to
10 matches
Mail list logo
