[Pkg-tigervnc-devel] Bug#768369: According to upstream they did not know the upper bound for buffer
Ondřej Surý
ondrej at sury.org
Tue Nov 18 05:30:24 UTC 2014
Bastien,
don't get me wrong. I think this is "serious" bug, but not with severity
"serious"[1] as this needs the user to do an explicit operation to
trigger the bug.
1. see https://www.debian.org/Bugs/Developer#severities:
Cheers,
Ondrej
On Mon, Nov 17, 2014, at 21:21, Bastien ROUCARIES wrote:
> Hi,
>
> For me it is a serious bug.
>
> According to http://sourceforge.net/p/libjpeg-turbo/bugs/64/?page=1
> (see http://sourceforge.net/p/libjpeg-turbo/bugs/64/?page=1):
>
> >Even though I'm doing the most I can to stack the deck in favor of the bug, it still only occurs once in about every 25 million iterations.
> >I have checked in your patch without modifications.
> >
> >So far, 130 bytes is the maximum I have been able to produce for a single MCU using the test, after literally a billion iterations. However, I am running it overnight so I can collect as many cases of >degenerate input images as I can, so I can hopefully determine what the upper bound is for the local buffer.
>
> Thus I am tented to add it is a true bug.
>
> Bastien
--
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
More information about the Pkg-tigervnc-devel
mailing list