Hello,
anyone who knows his way around Wiresharks exception code (or C's
setlongjmp
etc statements). If so, please have a look at bug 1001.
thanks
Joerg
On Wed, Jul 26, 2006 at 01:55:11PM +0000, bugzilla-daemon@xxxxxxxxxxxxx wrote:
> http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1001
>
> ------- Comment #2 from gentoo-a7x@xxxxxxxxxxxxxxx 2006-07-26 13:55 GMT -------
> I have confirmed that this problem occurs when stack smashing protection is
> turned on -- recompiling without SSP works. I don't know much about how SSP
> works, but I can see three possibilities: a bug in the SSP code, a minor bug
> in Wireshark that goes undetected until SSP is turned on, or a bug in Wireshark
> that could present a security problem.
--
Joerg Mayer <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
