xlockmore - serious security issue

Tarc tarc at tarc.po.cs.msu.su
Tue Jun 13 18:07:35 UTC 2006

> Ask me - we should mark this port forbidden and/or make
> and entry in vuxml until we resolve this issue. Let's make
> blank screen the default behavior or something. To leave
> this as is is unacceptable.

It's not good idea.
I use ently updated lockmore several years and I never have any problems, except one: if I turn option `BAD_PAM' off, I'll never lockout my X11 display.
my configs are:


other options are turned off.

`make -V CONFIGURE_ARGS' says:
--with-x  --without-motif  --disable-gtktest --without-gtk --without-gtk2  --without-nas --without-esound --without-rplay --without-editres --without-dtsaver --with-mesa --enable-bad-pam --enable-pam --enable-use-mb --enable-syslog --x-libraries=/usr/X11R6/lib --x-includes=/usr/X11R6/include --prefix=/usr/X11R6 i386-portbld-freebsd7.0

today's `uname -a' output is
FreeBSD tarc.po.cs.msu.su 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon May 22 04:49:15 MSD 2006     toor at tarc.po.cs.msu.su:/usr/obj/usr/src/sys/GENERIC  i386

   Best regards,
   	Arseny Nasokin

More information about the freebsd-ports mailing list