Bug#693087: segfault in xscreensaver, screen revealed

2012-11-15 Thread Adam D. Barratt
clone 693087 -1 -2 -3 reassign -1 ftp.debian.org user ftp.debian@packages.debian.org usertags -1 rm retitle -1 RM: pam-rsa -- RoST; unmaintained, buggy and dangerous user release.debian@packages.debian.org reassign -2 release.debian.org usertags -2 rm retitle -2 RM: pam-rsa -- RoST;

Bug#693087: segfault in xscreensaver, screen revealed

2012-11-14 Thread Yves-Alexis Perez
Control: clone -1 -2 -3 Control: reassign -2 ftpmasters Control: retitle -2 RM: pam-rsa -- RoST; unmaintained, buggy and dangerous Control: reassign -3 release.debian.org Control: retitle -3 RM: pam-rsa -- RoST; unmaintained, buggy and dangerous Control: user release.debian@packages.debian.org

Bug#693087: segfault in xscreensaver, screen revealed

2012-11-13 Thread Jan Lieskovsky
Thank you for your report, Ian. Package: libpam-rsa Version: 0.8-9-2.4 Tags: security * What led up to the situation? 1. I manually locked my screen using xscreensaver-command -lock. 2. I moved the pointer, causing the xscreensaver password screen to appear. 3. I moved the pointer some

Bug#693087: segfault in xscreensaver, screen revealed

2012-11-13 Thread Ian Zimmerman
Jan Is it possible to reproduce that xscreensaver crash also without Jan libpam-rsa module being used? (when using pam-unix login Jan alternative with the same scenario) No, it doesn't happen with pam-unix. This had been kicked around the debian security team for a couple of days before this

Bug#693087: segfault in xscreensaver, screen revealed

2012-11-13 Thread Yves-Alexis Perez
On mar., 2012-11-13 at 09:00 -0800, Ian Zimmerman wrote: Jan Is it possible to reproduce that xscreensaver crash also without Jan libpam-rsa module being used? (when using pam-unix login Jan alternative with the same scenario) No, it doesn't happen with pam-unix. This had been kicked around

Bug#693087: segfault in xscreensaver, screen revealed

2012-11-12 Thread Ian Zimmerman
Package: libpam-rsa Version: 0.8-9-2.4 Tags: security * What led up to the situation? 1. I manually locked my screen using xscreensaver-command -lock. 2. I moved the pointer, causing the xscreensaver password screen to appear. 3. I moved the pointer some more and waited for the timeout to expire.