Bug#907500: Seccomp enabled much earlier
Hi Christian, On Wed, Aug 29, 2018 at 07:26:56AM +0200, Christian Ehrhardt wrote: > Hi, > quote: > "seccomp support is enabled for the Debian builds only starting from > 1:2.12+dfsg-2, issue would be present already before source-wise, but going > to mark the issue as no-dsa for older versions" > > IMHO I'd think it is enabled since 1.3.0+dfsg-2exp quite a while back. > The latter changes are sometimes enabling additional architectures, but > "enabled" and thereby potentially affected it was way more back in time. Yes you are right, that my initial triaging was not correct. Still not sure if we want to treat this as DSA, or postpone it, but I have at least now reverted the wrong comment in the security-tracker. Thanks for spotting my mistake, corrected! Salvatore
Bug#907500: Seccomp enabled much earlier
Hi, quote: "seccomp support is enabled for the Debian builds only starting from 1:2.12+dfsg-2, issue would be present already before source-wise, but going to mark the issue as no-dsa for older versions" IMHO I'd think it is enabled since 1.3.0+dfsg-2exp quite a while back. The latter changes are sometimes enabling additional architectures, but "enabled" and thereby potentially affected it was way more back in time. Picking a random build log in unstable of 2014 [1] has --enable-seccomp as well as later on the proper detection on the configure run seccomp support yes [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=2.0.0%2Bdfsg-6%2Bb1=1402079442=0 -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd
