From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Holler <holler@ahsoftware.de>
Cc: David Howells <dhowells@redhat.com>,
rusty@rustcorp.com.au, torvalds@linux-foundation.org,
keyrings@linux-nfs.org, Josh Boyer <jwboyer@redhat.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] X.509: Remove certificate date checks
Date: Thu, 14 Mar 2013 17:09:24 +0000 [thread overview]
Message-ID: <1363280964.4853.89.camel@i7.infradead.org> (raw)
In-Reply-To: <5141F952.8000204@ahsoftware.de>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
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
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2013-03-14 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 12:34 David Howells
2013-03-14 12:48 ` David Woodhouse
2013-03-14 16:22 ` Alexander Holler
2013-03-14 17:09 ` David Woodhouse [this message]
2013-03-14 17:42 ` Alexander Holler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1363280964.4853.89.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=dhowells@redhat.com \
--cc=holler@ahsoftware.de \
--cc=jwboyer@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome