All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: dhowells@redhat.com, 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: Wed, 03 Feb 2016 16:25:53 +0000	[thread overview]
Message-ID: <28958.1454516753@warthog.procyon.org.uk> (raw)
In-Reply-To: <20160120153042.14d86d0b@lxorguk.ukuu.org.uk>

One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> wrote:

> 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.

As far as I can tell without actually buying a copy of ISO 8601, that standard
only allows for a single leap second in a day.

I grant that that doesn't mean that other standards may permit multiple leap
seconds.

David

  parent reply	other threads:[~2016-02-03 16:25 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 [this message]
2016-02-03 16:28     ` David Howells
2016-02-04 17:38       ` One Thousand Gnomes

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=28958.1454516753@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=David.Woodhouse@intel.com \
    --cc=arnd@arndb.de \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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.