From owner-freebsd-questions Fri Mar 1 16:42: 1 2002 Delivered-To: freebsd-questions@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 0B3D237B400 for ; Fri, 1 Mar 2002 16:41:59 -0800 (PST) Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id AE4F45D04; Fri, 1 Mar 2002 16:41:58 -0800 (PST) To: Cliff Sarginson Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Locking the screen In-reply-to: Your message of "Fri, 01 Mar 2002 20:28:07 +0100." <20020301192807.GB2147@raggedclown.net> Date: Fri, 01 Mar 2002 16:41:58 -0800 From: "Kevin Oberman" Message-Id: <20020302004158.AE4F45D04@ptavv.es.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Fri, 1 Mar 2002 20:28:07 +0100 > From: Cliff Sarginson > 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. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message