Date: Thu, 14 Dec 2023 08:01:38 +0800 From: Philip Paeps <philip@freebsd.org> To: Xin LI <delphij@gmail.com> Cc: FreeBSD Security Team <secteam@freebsd.org>, Xin Li <delphij@delphij.net>, src-committers <src-committers@freebsd.org>, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org, Warner Losh <imp@bsdimp.com> Subject: Re: git: b1c95af45488 - main - rc.conf: correct $ntp_leapfile_sources Message-ID: <D7508B7E-12AA-4A16-9A81-7F70A12AE92C@freebsd.org> In-Reply-To: <CAGMYy3sFFOXqvZHn_W83n6=X6ZFjUEQ8G3HCHtLxJf8sAV1v0Q@mail.gmail.com> References: <202312070550.3B75o8WV066387@gitrepo.freebsd.org> <CANCZdfrSitY2W%2B7EVaa_yX=KhsJNq_FZqyOLnBeTZX_-6YGxpg@mail.gmail.com> <389AB29C-D5C0-4091-91ED-219F33351B35@freebsd.org> <d75b041f-05f8-44c1-8de6-1fef89b7e537@delphij.net> <20231207222716.obSthG6r@steffen%sdaoden.eu> <CANCZdfpHWRECi=DyhxJAW4MkA-CyPLK=OSdSwBdKQJ57MyPwNA@mail.gmail.com> <20231208010731.3hijmSTL@steffen%sdaoden.eu> <CANCZdfrQU-7yXbzMT8fCmBp=w=CqTVWCgwdXJNXXcHBiOb7vvw@mail.gmail.com> <20231208171712.nWToJe0v@steffen%sdaoden.eu> <CAGMYy3sFFOXqvZHn_W83n6=X6ZFjUEQ8G3HCHtLxJf8sAV1v0Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-12-14 06:02:28 (+0800), Xin LI wrote: > I've written a draft errata at > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275419#c27 . Thanks. I think it's worth doing an EN for this, but I'd rather do it when the IANA leap-seconds.list file is updated. Otherwise we'll get complaints from folks who have installed the EN but note their leap-seconds.list still complains of imminent / past expiry. Regardless of whether we do an EN, I do think we should do an announcement (possibly signed by security-officer@) that the imminent expiry of leap-seconds.list is not an actual problem. No leap second will be introduced at the end of 2023. > Have we decided to go with the IANA location? If so we should include > philip's change above too. I believe IANA Is the best upstream for leap-seconds.list. IERS is really authoritative but there are copyright concerns (no public domain in France). NIST's version has no copyright concerns but is only available over FTP (and it's 2023. > I think we should issue an EN for at least the first two so FreeBSD > systems > won't go to IETF until ~mid 2024. Can someone (other from myself :) > from > secteam@ help with the actual EN process? I'll pick this up. Thanks for the draft! Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D7508B7E-12AA-4A16-9A81-7F70A12AE92C>