Date: Tue, 13 Jun 2006 22:09:07 +0400 From: Tarc <tarc@tarc.po.cs.msu.su> To: freebsd-ports@freebsd.org Subject: Re: xlockmore - serious security issue Message-ID: <20060613180907.GI22799@tarc.po.cs.msu.su> Resent-Message-ID: <20060613181003.GA857@tarc.po.cs.msu.su> In-Reply-To: <cb5206420606130751s65808df2rb39b2ebb163757c4@mail.gmail.com> References: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com> <20060613113151.GC8105@heechee.tobez.org> <cb5206420606130454i2c4fac71m53c7b2d81839e7dd@mail.gmail.com> <200606131037.58401.amistry@am-productions.biz> <cb5206420606130751s65808df2rb39b2ebb163757c4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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: WITH_MESAGL WITH_MB WITH_PAM WITH_BAD_PAM 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@tarc.po.cs.msu.su:/usr/obj/usr/src/sys/GENERIC i386 -- Best regards, Arseny Nasokin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060613180907.GI22799>