reassign 345728 libruby1.8 severity 345728 important tags 345728 moreinfo thanks
On Tue, Jan 03, 2006 at 07:33:29AM +0100, Rafal Maj wrote: > apt-listbugs causes libsafe libc calls to detect access violation > Im not shure is it apt-listbug or ruby? > I suppose interpretor should never allow, even buggy program, to crash > or make the itnerpreter corrupt own stack/memory which could mean that > ruby have security hole (assuming it is not fault of libsafe that is > reporting a false-positive) Please provide evidence of the actual bug in ruby which would be exploitable during normal operation and warrant an RC severity. There have been other bug reports involving libsafe which it has been suggested are libsafe bugs, *not* bugs in the application. For a tool whose job it is to identify overflow bugs in applications, so far the libsafe backtraces I've seen have been pretty damn useless for debugging. > so I report it as Ruby bug You didn't; you reported it as a bug against "/usr/bin/apt-listbug", which is invalid. Reassigning to the libruby1.8 package, since that's apparently where it belongs. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
