From owner-freebsd-security@freebsd.org  Thu Jul  2 08:43:28 2015
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6D60993E7D
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Thu,  2 Jul 2015 08:43:28 +0000 (UTC) (envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id 7ABAF1649;
 Thu,  2 Jul 2015 08:43:28 +0000 (UTC) (envelope-from des@des.no)
Received: from nine.des.no (smtp.des.no [194.63.250.102])
 by smtp-int.des.no (Postfix) with ESMTP id 1C0914669;
 Thu,  2 Jul 2015 08:43:25 +0000 (UTC)
Received: by nine.des.no (Postfix, from userid 1001)
 id BE69B1D06; Thu,  2 Jul 2015 10:43:24 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Leif Pedersen <bilbo@hobbiton.org>
Cc: Mark Felder <feld@freebsd.org>,
 "freebsd-security\@freebsd.org" <freebsd-security@freebsd.org>
Subject: Re: Leap Second
References: <CAA3htvuv0Emy5SazXzYNZegKzS-Z4=tc3ua8Ca6GMgeTj99n7A@mail.gmail.com>
 <1435154274.964221.306546033.052903CD@webmail.messagingengine.com>
 <86bnfwxa4m.fsf@nine.des.no>
 <1435758941.105242.312562265.3103CECB@webmail.messagingengine.com>
 <CAK-wPOjqZUPnWSbgXYt+ghu1BHUK7E=dUVU=oW8+0p7ywzN4Wg@mail.gmail.com>
Date: Thu, 02 Jul 2015 10:43:23 +0200
In-Reply-To: <CAK-wPOjqZUPnWSbgXYt+ghu1BHUK7E=dUVU=oW8+0p7ywzN4Wg@mail.gmail.com>
 (Leif Pedersen's message of "Wed, 1 Jul 2015 12:46:21 -0500")
Message-ID: <86oajvvtjo.fsf@nine.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2015 08:43:28 -0000

Leif Pedersen <bilbo@hobbiton.org> writes:
> Is there a reasonable way to enable awareness of leap-seconds while
> syncing with ntpd? That is to say, how can I get the system to include
> leap-seconds in calculating `date +%s`, without having `date` be off
> by 26[1] seconds?

No.  POSIX deals with leap seconds by pretending they don't exist.

> I tried setting /etc/localtime to UTC including leap-seconds [...]
> However, ntpd continues to sync the clock (from pool.ntp.org) in
> ignorance of leap-seconds. [...] Can ntpd undo the leap-seconds
> inserted by ntp.org? Or is there another NTP pool that would work for
> me?

NTP works in UTC as well.  The pool does not set the clock; all it does
is coordinate servers who claim to know the correct time.  I guess you
could try to convince the ISC and JHU to add a TAI offset field to the
next version of the NTP protocol...

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no