Date: Tue, 30 Jun 1998 02:36:39 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: andrewr <andrewr@slack.net> Cc: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>, freebsd-security@FreeBSD.ORG Subject: Re: xlock Message-ID: <19980630023639.02857@hydrogen.nike.efn.org> In-Reply-To: <Pine.NEB.3.96.980629081835.12717A-100000@brooklyn.slack.net>; from andrewr on Mon, Jun 29, 1998 at 08:27:49AM -0400 References: <199806290632.IAA00836@gilberto.physik.RWTH-Aachen.DE> <Pine.NEB.3.96.980629081835.12717A-100000@brooklyn.slack.net>
next in thread | previous in thread | raw e-mail | index | archive | help
andrewr scribbled this message on Jun 29: > Also, I am porting a console locking program (doesn't allow VT switching), > from linux, but I have been having trouble with the actual stopping of the > allowing of VT switching. I have tried setting vtmode to be handled by > the process, then using an ioctl to execute this. This failed. Then, I > tried using flock(), that failed. If you have any ideas and would like to > know what I did before (dealing with flock() and ioctl(), just ask). I have modifications to lock that does this... it really isn't hard... you just simply modify the relsig of vt_mode to a signal, and simply ignore the signal... syscons will only switch away when you tell it that it can... this is how X restores the video mode for syscons... > On Mon, 29 Jun 1998, Christoph Kukulies wrote: > > > > > Alarmed by recent buffer overflow attacks on Linux machines in > > my vicinity (an exploit for this is available) I thought about > > xlock under FreeBSD and would like to know whether the > > security hole has been sorted out under FreeBSD 2.2.x or what > > measures are advised to prevent it. p.s. why do people not spend the 2 seconds it takes to remove sigs?? -- John-Mark Gurney Voice: +1 541 683 7109 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD Don't trust anyone you don't have the source for To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980630023639.02857>