From owner-freebsd-hackers Mon Oct 23 11:15:45 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA15404 for hackers-outgoing; Mon, 23 Oct 1995 11:15:45 -0700 Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA15399 for ; Mon, 23 Oct 1995 11:15:40 -0700 Received: (from news@localhost) by haywire.DIALix.COM (sendmail) id CAA19128 for freebsd-hackers@freebsd.org; Tue, 24 Oct 1995 02:15:23 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: 24 Oct 1995 02:14:48 +0800 From: peter@haywire.dialix.com (Peter Wemm) Message-ID: <46gm2o$ikl$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <9510231408.AA00655@sunny.wup.de> Subject: Re: (fwd) CERT Advisory CA-95:13 - Syslog Vulnerability (with sendmail workaround) Sender: owner-hackers@freebsd.org Precedence: bulk andreas@sunny.wup.de (Andreas Klemm) writes: >Hi ! >Do you know this CERET Advisory already ?! >Strange for me, that a Linux version with a certain libc release >is 1. proofed by CERT and 2. mentioned to be secure and >FreeBSD isn't mentioned ..... what does it mean ... > a) CERT doesn't test FreeBSD ? > b) FreeBSD still has the mentioned security hole ? >Regards > Andreas /// FreeBSD has fixed the hole, IMHO better than the others, but it used one of the advanced 4.4BSD stdio features to do it more securely (fwopen()/vfprintf() instead of umpteen strlen()/snprintf()). They covered FreeBSD/NetBSD (not by name) by saying: there are different patches available for other operating systems, but these have not been evaluated by cert, blah, blah. Both Free/NetBSD did it their own way. -Peter >-- >andreas@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH >Andreas Klemm ___/\/\/ - Support Unix -