From owner-freebsd-hackers Fri Aug 14 10:47:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05728 for freebsd-hackers-outgoing; Fri, 14 Aug 1998 10:47:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shasta.wstein.com (shasta.wstein.com [206.163.206.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05721 for ; Fri, 14 Aug 1998 10:47:36 -0700 (PDT) (envelope-from joes@shasta.wstein.com) Received: (from joes@localhost) by shasta.wstein.com (8.9.0/8.9.0) id KAA20357; Fri, 14 Aug 1998 10:46:55 -0700 (PDT) From: Joseph Stein Message-Id: <199808141746.KAA20357@shasta.wstein.com> Subject: Re: 64-bit time_t In-Reply-To: <199808141733.LAA24664@lariat.lariat.org> from Brett Glass at "Aug 14, 98 11:33:25 am" To: brett@lariat.org (Brett Glass) Date: Fri, 14 Aug 1998 10:46:55 -0700 (PDT) Cc: mike@smith.net.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett Glass allegedly wrote: > Security is also a safety issue. Use safe tools, and you're less likely > to create security holes. There is no such thing as a "safe" tool. You can write code in assembly language and still end up with security holes. Until someone writes a compiler (for *any* compiled language) that will test for every possible conceivable security holes (volunteers needed...) there will be security holes in *every* application -- that can be fixed when found, using, the "unsafe" tool that was used to create it. My 2c on this issue. -- Joseph Stein; Beaverton, Oregon USA email: joes@wstein.com Finger joes@shasta.wstein.com for contact information and PGP Public Key! Oregon FirePage http://www.ofp.org [OFP-504] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message