* Yves-Alexis Perez <corsac@debian.org>, 2016-03-02, 12:46:
I did a quick check on a local mirror (which might be incomplete), and found three packages with errors:dpkg -c debian/pool/main/s/sed/sed_4.2.2-4+b1_amd64.deb |grep bin/$ drwxrwxr-x root/root 0 2014-11-08 19:28 ./bin/ dpkg -c debian/pool/main/l/lpe/lpe_1.2.7-2_amd64.deb|grep bin/$ drwxrwxr-x root/root 0 2014-12-24 23:14 ./usr/bin/ dpkg -c debian/pool/main/u/ucspi-proxy/ucspi-proxy_0.99-1_amd64.deb|grep bin/$ drwxrwxr-x root/root 0 2014-08-10 18:08 ./usr/bin/
[...]
It looks like an umask problem at package build time. Right now it doesn't seem to have obvious security issues (like world writable /bin) but I'm not too sure there are not other stuff hidden.It seems to me that lintian looks at testing/unstable (at least looking at https://lintian.debian.org/full/clint@debian.org.html#sed_4.2.2-6), so I'm not sure this would help for stable.I guess it'd make sense to do an archive-wide lintian run to look for that kind of mistakes, and then ask for stable binNMUs of the relevant packages.
Yup, lintian.d.o only checks unstable. For sed, this is #774347, which is already fixed there.
so as far as I can tell there was no reaction from -release (although I can understand noone's really sure what to do here). Is it at least possible to schedule binNMUs in stable for those affected packages so future installs don't end up with bad permissions like these?
I believe sbuild uses umask 002, so binNMUs probably won't help. In fact, the stable version of sed was already built on buildds.
-- Jakub Wilk