From nobody Wed Dec 13 22:56:11 2023 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sr9p15T1Rz54S8K for ; Wed, 13 Dec 2023 22:56:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sr9p151Gxz3YQV for ; Wed, 13 Dec 2023 22:56:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2c9f8faf57bso96125731fa.3 for ; Wed, 13 Dec 2023 14:56:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1702508183; x=1703112983; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ap81MLYlaSvs4YwcR2P1n9fjxhf5mzIHXXyCGOWg9u4=; b=xhX7oD2YlxxsGqDQxvfsK7CFywb4e+rj69tDemXGUL+CgpbkEvU3L6R4dTTQUJ2dQl IGHat7SFXX/HniDToF7vBng8fpdT2DaDoTjMy1FDJwmzw6pDFftd8zeh3FVYB7X+NykT 6zGryaljvLeDC2zOHr2YKfkYVx3r3sKUIL49Uz3VMZmhobkLYEDUPd0sxXDBZvuz7Tgl jCjbie+VHMsrro6XOPg2atwnmGqT6Ifzx0FOZY4luSBQhxXde8GXSpxx890HS/hCNwqs 29oUR0jPchTodqkhmEaMWPPPV1GhbvNLW7UU82sc8AsM0786HC502D9ghh6EYi1rcMQg vu8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702508183; x=1703112983; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ap81MLYlaSvs4YwcR2P1n9fjxhf5mzIHXXyCGOWg9u4=; b=oSsL2qvPLohCm6sZee5Z7rd5g2BJBM7a5tGJrc6gX5iVNJUK4k3fY3RYbjlGNgFSYG rSKAPypxaGsJcOyUWIGDKle9vM11p7lZvWcJD2U+17NOTYZpX+igt5I7wiKje6O0m94q QgDbcV6Eg2xFtBCAwqA9RY3swgZlU72Vbt+uq/30Nq6OUic4TSfyFO0xD4GQ1RSsEnWY NbqMZs7OlcaoVMeL7dYK61DHuAOyNmc9fgTuV3kW7qM+PrLIM4wJvtJvxmMiA1ybfyL5 LusPfYJOXsCQG4kRAXdM14nNQFS9pRQY+duIS+BXMByZ1s1EKmtKGIKliBKShCvYHGh/ Ubjw== X-Gm-Message-State: AOJu0YxNGV7FUgyVd+QC7xBSlaTnCdktYfUNmN0w1+Px+t1AO85BAxwZ EJHwcMsdJKQYf1W6e6eDduj/0yRs8W8FnIFYlkJVuHyl7Mp8oRcade0= X-Google-Smtp-Source: AGHT+IGLvPvZ4VXwz/9qvQt6FflPy/4mRM0LtjnnMBZ/KRp7FeCUg6kT4tR2T7FtTAdsfaYAz4zqwlJc/c2P5h2eGlU= X-Received: by 2002:a05:651c:2111:b0:2cc:1fae:e3e1 with SMTP id a17-20020a05651c211100b002cc1faee3e1mr3725426ljq.24.1702508183255; Wed, 13 Dec 2023 14:56:23 -0800 (PST) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <51e78f56-b5f1-4910-b217-fdeef0d95bd7@quip.cz> In-Reply-To: <51e78f56-b5f1-4910-b217-fdeef0d95bd7@quip.cz> From: Warner Losh Date: Wed, 13 Dec 2023 15:56:11 -0700 Message-ID: Subject: Re: ntpd: leap-seconds.list expiration To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Michael Proto , FreeBSD-STABLE Mailing List Content-Type: multipart/alternative; boundary="0000000000007d9663060c6c1346" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4Sr9p151Gxz3YQV --0000000000007d9663060c6c1346 Content-Type: text/plain; charset="UTF-8" On Wed, Dec 13, 2023, 3:47 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > On 13/12/2023 05:03, Michael Proto wrote: > > Noticed recently (in both my upgraded and newly-installed hosts) that > > the leap-seconds.list file is in danger of expiration very soon (12/28). > > It appears the default download location in /etc/defaults/rc.conf > > (https://www.ietf.org/timezones/data/leap-seconds.list > > ) no longer > > carries this file, or at least it says plainly so when I try to fetch it. > > > > I've been able to work around it locally by > > setting ntp_leapfile_sources=" > https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list < > https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list>" in > /etc/rc.conf from IERS, though in searching where to fetch this there are > questions of copyright in regards to distribution so while this should work > for end-users I don't know how applicable this would be upstream (submitted > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275737 < > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275737>). I figured I'd > throw it out here for visibility to operators as my workaround should work > in that case. > It's not at all clear there are issues with redistribution. Any files that require a license or purchase are locked down at the web server level. The issues sound more on the FUD end of the scale. BIPM has never tried to enforce any ip claims to this file. They have, many years ago, displayed an ignorance of what people want in terms of a clear grant... the bipm, or it's subsidiaries, has published all kinds of other data that's clearly more valuable. Leap seconds are a fact that has low to no creative content. It's not even clear you could copyright it... the comments maybe... but I'm not seeing any kind of real risk here. Warner Thank you for this link! I tried to find actual file yesterday. Now I > fixed it in ntp_leapfile_sources on all my machines. > > Best regards > Miroslav Lachman > > --0000000000007d9663060c6c1346 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Dec 13, 2023, 3:47 PM Miroslav Lachman <000.fbsd@quip.cz> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">On 13/12/2023 05:03, Michael Proto wrote:
> Noticed recently (in both my upgraded and newly-installed hosts) that =
> the leap-seconds.list file is in danger of expiration very soon (12/28= ).
> It appears the default download location in /etc/defaults/rc.conf
> (https://www.ietf.org/timezones= /data/leap-seconds.list
> <https://www.ietf.org/timezo= nes/data/leap-seconds.list>) no longer
> carries this file, or at least it says plainly so when I try to fetch = it.
>
> I've been able to work around it locally by
> setting=C2=A0ntp_leapfile_sources=3D"https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.lis= t <https://hpiers.obspm= .fr/iers/bul/bulc/ntp/leap-seconds.list>" in /etc/rc.conf from = IERS, though=C2=A0in searching where to fetch this there are questions of c= opyright in regards to distribution so while this should work for end-users= I don't know how applicable this would be upstream (submitted https://bugs.freebsd.org/bugzilla/show= _bug.cgi?id=3D275737 <ht= tps://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275737>). I figure= d I'd throw it out here for visibility to operators as my workaround sh= ould work in that case.

<= /div>
It's not at all clear there are issues with redi= stribution. Any files that require a license or purchase are locked down at= the web server level. The issues sound more on the FUD end of the scale. B= IPM has never tried to enforce any ip claims to this file. They have, many = years ago, displayed an ignorance of what people want in terms of a clear g= rant... the bipm, or it's subsidiaries, has published all kinds of othe= r data that's clearly more valuable. Leap seconds are a fact that has l= ow to no creative content. It's not even clear you could copyright it..= . the comments maybe... but I'm not seeing any kind of real risk here.<= /div>

Warner


Thank you for this link! I tried to find actual file yesterday. Now I
fixed it in ntp_leapfile_sources on all my machines.

Best regards
Miroslav Lachman

--0000000000007d9663060c6c1346--