From owner-freebsd-security Tue Nov 3 23:11:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04891 for freebsd-security-outgoing; Tue, 3 Nov 1998 23:11:27 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from aniwa.sky (p14-max11.wlg.ihug.co.nz [209.78.48.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04881 for ; Tue, 3 Nov 1998 23:11:23 -0800 (PST) (envelope-from andrew@squiz.co.nz) Received: from localhost (andrew@localhost) by aniwa.sky (8.8.8/8.8.7) with SMTP id UAA05299; Wed, 4 Nov 1998 20:10:15 +1300 (NZDT) (envelope-from andrew@squiz.co.nz) Date: Wed, 4 Nov 1998 20:10:00 +1300 (NZDT) From: Andrew McNaughton X-Sender: andrew@aniwa.sky Reply-To: andrew@squiz.co.nz To: Nicholas Charles Brawn cc: Warner Losh , FreeBSD-security@FreeBSD.ORG Subject: Re: [rootshell] Security Bulletin #25 (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 4 Nov 1998, Nicholas Charles Brawn wrote: > Well I just grabbed 1.2.26 and did: > find . -exec grep sprintf {} \; |wc -l > > And came up with 138 lines. Just having sprintf() in your code is not > indicative of a vulnerability, but it's still a high number. ssh is commonly used for piping substantial ammounts of data, and can probably claim good reasons for using the faster non-bounds-checking routines in many of these cases. Doesn't apply to low volume things like the logging routines though. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message