From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: Rudolf Polzer <rpolzer@google.com>,
keyrings@vger.kernel.org,
David Woodhouse <David.Woodhouse@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
John Stultz <john.stultz@linaro.org>
Subject: Re: [RFC PATCH 4/4] X.509: Handle midnight alternative notation in GeneralizedTime
Date: Thu, 4 Feb 2016 17:38:11 +0000 [thread overview]
Message-ID: <20160204173811.0c21dcbf@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <29160.1454516921@warthog.procyon.org.uk>
On Wed, 03 Feb 2016 16:28:41 +0000
David Howells <dhowells@redhat.com> wrote:
> One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> wrote:
>
> > > > As for 24:xx:yy times - I'm split about this. This code doesn't
> > > > require a bijective decoding anyway (and if it did, 24:00:00 and
> > > > 00:00:00 mapping to the same time64_t would be problem enough) so this
> > > > is sure safe. On the other hand, a cert with a 24:xx:yy time that's
> > > > not 24:00:00 probably should be regarded as invalid and not trusted
> > > > for that reason alone.
> > >
> > > Feel free to argue that one with Linus:-/
> >
> > Pedantic hat on 24:00:01 is also potentially valid. The ANSI and ISO
> > standards allow for double leap seconds even though CCIR-460 doesn't
> > allow it to actually happen.
>
> Did you mean 24:00:01 or 23:59:61?
I'd have to actually go and real all the standards for that one.
Alan
prev parent reply other threads:[~2016-02-04 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 22:16 [PATCH 0/4] X.509: Fix time handling David Howells
2016-01-04 22:17 ` [RFC PATCH 1/4] X.509: Fix leap year handling again David Howells
2016-01-20 15:12 ` Rudolf Polzer
2016-01-20 15:18 ` David Howells
2016-01-04 22:17 ` [RFC PATCH 2/4] Handle ISO 8601 leap seconds and encodings of midnight in mktime64() David Howells
2016-01-04 22:17 ` [RFC PATCH 3/4] X.509: Support leap seconds David Howells
2016-01-20 15:08 ` Rudolf Polzer
2016-01-04 22:17 ` [RFC PATCH 4/4] X.509: Handle midnight alternative notation in GeneralizedTime David Howells
2016-01-20 15:08 ` Rudolf Polzer
2016-01-20 15:20 ` David Howells
2016-01-20 15:30 ` One Thousand Gnomes
2016-02-03 16:25 ` David Howells
2016-02-03 16:28 ` David Howells
2016-02-04 17:38 ` One Thousand Gnomes [this message]
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=20160204173811.0c21dcbf@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=David.Woodhouse@intel.com \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=john.stultz@linaro.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rpolzer@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.