Date: Fri, 1 Mar 2002 21:38:32 -0500 From: "Scott M. Nolde" <scott@smnolde.com> To: Kevin Oberman <oberman@es.net> Cc: Cliff Sarginson <csfbsd@raggedclown.net>, freebsd-questions@FreeBSD.ORG Subject: Re: Locking the screen Message-ID: <20020301213832.A32060@smnolde.com> In-Reply-To: <20020302004158.AE4F45D04@ptavv.es.net>; from oberman@es.net on Fri, Mar 01, 2002 at 04:41:58PM -0800 References: <20020301192807.GB2147@raggedclown.net> <20020302004158.AE4F45D04@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman(oberman@es.net)@2002.03.01 16:41:58 +0000: > > Date: Fri, 1 Mar 2002 20:28:07 +0100 > > From: Cliff Sarginson <csfbsd@raggedclown.net> > > Sender: owner-freebsd-questions@FreeBSD.ORG > > > > On Fri, Mar 01, 2002 at 01:02:26PM -0500, Dan Peck wrote: > > > > > > If your looking for an X based program, xscreensaver > > > (/usr/ports/x11/xscreensaver) has a locking option. > > > > Bear in mind of course that if you are trying to lock any access to the > > system the X lock is totally useless, since people can just alt/f to > > another virtual console. > > That's not the real problem as the other vtys should not be logged > in. The real threat is CTRL-ALT-BS. That leaves you with a live vty and > no protection on it. I think [gkx]dm is a far safer way to deal with > this. You can always alias startx='startx;exit'. That way if your X session logged out or Ctrl-Alt-BS out the user would be at a login prompt. Combine that with a X screen lock and you might be better protected. > > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > -- Scott Nolde GPG Key 0xD869AB48 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020301213832.A32060>