From owner-freebsd-current Tue May 26 20:24:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02383 for freebsd-current-outgoing; Tue, 26 May 1998 20:24:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m2.findmail.com (m2.findmail.com [209.185.96.135]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA02357 for ; Tue, 26 May 1998 20:24:29 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 16264 invoked by uid 505); 27 May 1998 03:23:29 -0000 Date: 27 May 1998 03:23:29 -0000 Message-ID: <19980527032329.16263.qmail@m2.findmail.com> From: "Brian Feldman" Subject: current instabilities To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1) Heads up Julian, Luoqi, it took an amazing 6 days but SoftUpdates FINALLY crashed during a make -j4 world; the panic was dangling deps, but I didn't save the core, so I lost it, besides the fact I'm sure vmcore's from SoftUpdates crashes aren't in short supply ;) But good job guys, you've got it stable enough to stay up almost a week 2) "options VM86" - EVIL EVIL EVIL! This really allows way too much access to the memory by a mortal, and it's an effective DoS attack if a user runs doscmd, say, and a certain executable (this time, I happened to try ZSnes). Think there may be a way to make this safer? (I locked myself up, and it didn't panic so I don't know what exact function caused it). Also, could USER_LDT possibly be used as a DoS attack, like it seems to me it could? Cheers, Brian Feldman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message