From owner-freebsd-security@freebsd.org Wed Jul 1 22:27:56 2015 Return-Path: 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 4F97B992961 for ; Wed, 1 Jul 2015 22:27:56 +0000 (UTC) (envelope-from bilbo@hobbiton.org) Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E21EF22B7 for ; Wed, 1 Jul 2015 22:27:55 +0000 (UTC) (envelope-from bilbo@hobbiton.org) Received: by wiwl6 with SMTP id l6so178967575wiw.0 for ; Wed, 01 Jul 2015 15:27:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=R28qHzSdgplGJi7MwRVpAYrOflowjRL4BfjCN5l+S6A=; b=lkbkvODpT5apkiz225zB2lDjKb7q4rxOBwvy+jGdT1AfUcWW3KFKGugGz3o3YtjkKm C0ND756njo6IwKFindzA9KP5jQEDyHin+oW1UC0Bib9FUgC8PfZZsAWmH399oRCQ3bzd HFytSkHMgIO8KlQrJrtQzjgeQVRTjamf07hnFEsjFbD9rD1NZnNoWwiBXR0SmfpLCoBj reP4kQ3R9yRpkHQeteukCZzmnu2UQ/J41owe4hAPUihqFvlMBqJy3P2tWotfKCeK+RE9 Lo5FNtXAb2ewSCtCD9exz61Q/of4VD+0FLg15Gf06Lqdd7q0/DUPykH2Ei9juyUd7K1N hYiA== X-Gm-Message-State: ALoCoQkPiHLNNVDGjB095S2o7/CkMSeIbLdKbiugsCv/cqAqG+1evyY0ACN6GcdYTNOlnn2gFl8o X-Received: by 10.180.9.225 with SMTP id d1mr48138370wib.73.1435789673303; Wed, 01 Jul 2015 15:27:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.159.207 with HTTP; Wed, 1 Jul 2015 15:27:13 -0700 (PDT) X-Originating-IP: [68.178.93.3] In-Reply-To: <20150701202728.GA9532@server.rulingia.com> References: <1435154274.964221.306546033.052903CD@webmail.messagingengine.com> <86bnfwxa4m.fsf@nine.des.no> <1435758941.105242.312562265.3103CECB@webmail.messagingengine.com> <20150701202728.GA9532@server.rulingia.com> From: Leif Pedersen Date: Wed, 1 Jul 2015 17:27:13 -0500 Message-ID: Subject: Re: Leap Second To: Peter Jeremy Cc: "freebsd-security@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2015 22:27:56 -0000 On Wed, Jul 1, 2015 at 3:27 PM, Peter Jeremy wrote: > > On 2015-Jul-01 12:46:21 -0500, Leif Pedersen wrote: > >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? > > ntpd(8) has provision for specifying a leapsecond file which presumably > makes it leap-second aware. I haven't looked into the details. > >From the docs, I'm fairly sure that the leap-second files don't stop NTP from fudging hardware clock, and only help it do so more gracefully. > There's also posix2time(3) to convert between a TAI-based time_t and a > POSIX-based time_t. posix2time(3) doesn't seem to have anything to do with setting the hardware clock. > > -- > Peter Jeremy -- As implied by email protocols, the information in this message is not confidential. Any middle-man or recipient may inspect, modify, copy, forward, reply to, delete, or filter email for any purpose unless said parties are otherwise obligated. As the sender, I acknowledge that I have a lower expectation of the control and privacy of this message than I would a post-card. Further, nothing in this message is legally binding without cryptographic evidence of its integrity. http://bilbo.hobbiton.org/wiki/Eat_My_Sig