Re: tiff / CVE-2018-18661

2018-11-14 Thread Brian May
Brian May writes: > I can reproduce CVE-2018-19210. Both on wheezy and stretch. Doesn't Me getting distributions confused. I tested on Jessie, and I was able to reproduce the problem. I did not test wheezy. -- Brian May

Re: tiff / CVE-2018-18661

2018-11-14 Thread Brian May
Brian May writes: > Ola Lundqvist writes: > >> Could it be so that the problem is only reproducible on 32-bit >> systems? > > Good point. Will try. Nope. Can't reproduce i386 build on amd64 kernel. I would be rather surprised if choice of kernel mattered. I can reproduce CVE-2018-19210. Both

Re: tiff / CVE-2018-18661

2018-11-14 Thread Brian May
Ola Lundqvist writes: > Could it be so that the problem is only reproducible on 32-bit > systems? Good point. Will try. -- Brian May

Re: tiff / CVE-2018-18661

2018-11-14 Thread Ola Lundqvist
Hi Could it be so that the problem is only reproducible on 32-bit systems? // Ola On Tue, 13 Nov 2018 at 07:30, Brian May wrote: > Ola Lundqvist writes: > > > Interesting. I wonder what the fix do differently in this case. It is a > > little worrying that it exit with a zero return code, but

Accepted rustc 1.24.1+dfsg1-1~deb8u2 (source amd64 all) into oldstable

2018-11-14 Thread Emilio Pozuelo Monfort
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Nov 2018 00:50:22 +0100 Source: rustc Binary: rustc libstd-rust-1.24 libstd-rust-dev rust-gdb rust-lldb rust-doc rust-src Architecture: source amd64 all Version: 1.24.1+dfsg1-1~deb8u2 Distribution: jessie-security Urgency: