lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 25 Oct 2011 11:09:17 +0300
From:	Jari Ruusu <jariruusu@...rs.sourceforge.net>
To:	Greg KH <greg@...ah.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: kernel.org tarball/patch signature files

Greg KH wrote:
> On Tue, Oct 25, 2011 at 09:06:37AM +0300, Jari Ruusu wrote:
> > How about signing just one compressed tarball/patch, and let other
> > compressed versions be without signature files. Users who want to check
> > signature will then download the one you signed.
> 
> That's no difference from what we are doing today if you think it
> though.

You signing compressed version eliminates exposure to yet undiscovered
decompressor bugs. Pre-emptively removing as many as possible attack
surfaces is the correct securely engineered way of doing things. You signing
decompressed version is opposite of that. You added new attack surface.

Decompressors are complex software. They almost certainly have bugs in
evil-formatted data handling, forever. Reading data from untrusted internet
and feeding that data to decompressor without any authentication, screams
"REMOTE EXPLOIT ME", if you look at it from security point of view.

> Yes, we are working on just that thing, and the foo.tar.sums file will
> be signed with the kernel.org "throwaway" key, so you can check that as
> well.

That sounds much better than current signing practice.

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ