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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1363280964.4853.89.camel@i7.infradead.org>
Date:	Thu, 14 Mar 2013 17:09:24 +0000
From:	David Woodhouse <dwmw2@...radead.org>
To:	Alexander Holler <holler@...oftware.de>
Cc:	David Howells <dhowells@...hat.com>, rusty@...tcorp.com.au,
	torvalds@...ux-foundation.org, keyrings@...ux-nfs.org,
	Josh Boyer <jwboyer@...hat.com>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: [PATCH] X.509: Remove certificate date checks

On Thu, 2013-03-14 at 17:22 +0100, Alexander Holler wrote:
> 
> Agreed (thats what my patch did).
> 
> I've introduced a new config option because I don't know if something (a 
> use case I don't know) relies on the validity check of the dates in the 
> parser. If there currently isn't such a user, just removing the validity 
> check in the parser might be enough. 

Is there *is* such a user, it's broken already. The key could have been
loaded (and passed the existing check) *months* ago, expired seconds
after it was loaded, and your hypothetical user could still be happily
trusting it.

> Offering the parsed dates for later usage is still a good idea.

Right.

-- 
dwmw2

Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (6171 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ