Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf.

2003-02-24 Thread Phil Edwards
On Mon, Feb 24, 2003 at 12:28:44AM -0800, Alexander Hvostov wrote: > As noted in the corresponding man page, the 'sprintf' and 'vsprintf' > functions are > insecure, and should not be used. I suggest that gcc print a warning when > compiling > code in which they are used, as it already does with

Processed: Re: Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf.

2003-02-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 182277 - security Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf. Tags were: security Tags removed: security > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking

Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf.

2003-02-24 Thread Matt Zimmerman
tags 182277 - security thanks On Mon, Feb 24, 2003 at 12:28:44AM -0800, Alexander Hvostov wrote: > Package: gcc-3.2 > Version: 1:3.2.3-0pre1 > Severity: normal > Tags: security > > As noted in the corresponding man page, the 'sprintf' and 'vsprintf' > functions are > insecure, and should not be

Bug#182277: gcc-3.2: Should print a warning when using (v)sprintf.

2003-02-24 Thread Alexander Hvostov
Package: gcc-3.2 Version: 1:3.2.3-0pre1 Severity: normal Tags: security -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As noted in the corresponding man page, the 'sprintf' and 'vsprintf' functions are insecure, and should not be used. I suggest that gcc print a warning when compiling code in wh