Date: Fri, 18 Aug 2000 00:51:53 -0600 From: Warner Losh <imp@village.org> To: Karl Pielorz <kpielorz@tdx.co.uk> Cc: hackers@FreeBSD.ORG Subject: Re: Critical (or equivalent) section in Userland? Message-ID: <200008180651.AAA18596@billy-club.village.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008180651.AAA18596>