From owner-freebsd-hackers Thu Aug 17 23:51:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 566E937B67F for ; Thu, 17 Aug 2000 23:51:56 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA38744; Fri, 18 Aug 2000 00:51:54 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id AAA18596; Fri, 18 Aug 2000 00:51:53 -0600 (MDT) Message-Id: <200008180651.AAA18596@billy-club.village.org> To: Karl Pielorz Subject: Re: Critical (or equivalent) section in Userland? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 18 Aug 2000 07:49:32 BST." <399CDC7C.F68E634@tdx.co.uk> References: <399CDC7C.F68E634@tdx.co.uk> <399C5201.5B6911CE@tdx.co.uk> <399BA212.A84240AE@tdx.co.uk> <200008171723.LAA12924@harmony.village.org> <200008172140.PAA14347@harmony.village.org> Date: Fri, 18 Aug 2000 00:51:53 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <399CDC7C.F68E634@tdx.co.uk> Karl Pielorz writes: : However, 'killall -SIGSTOP sendmail' - appears to work very nicely... With a : 'killall -SIGCONT sendmail' putting things back to normal. I'm also doing the : stop twice for good measure incase anything was forking at the time. No need to stop twice. : I guess only time will tell, but the signal idea seems the best so far, : considering the other restrictions :) Well, you still have the same problem as before, you've just made it harder to exploit. Namely, if sendmail fires up and reads one of the set of files, then you stop it, and start it again and reads the rest it is little different than the problem you had before. I would suspect it is much less likely to happen, however. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message