Re: prep for point release of NTPSec, suggest 2019-07-31

Mark Atwood via devel writes: > How does everyone feel about next Saturday, Aug 31 2019-07-31? You've got a time machine? 8-) Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.ht

Re: Interesting talk on Chronos

Mark Atwood via devel writes: > Any updates or thoughts? I don't see it solving any real problem. When you assume an attacker of the strength needed for it to be effective, then he'd surely have more effective ways to mess with your network. Also, as long as it doesn't use both DNSSEC and NTS an

Re: prep for point release of NTPSec, suggest 2019-07-31

> How does everyone feel about next Saturday, Aug 31 2019-07-31? Looks good to me. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel

Re: ALPN checking

> Hal, 203.123.48.1 has been downgraded to NTPsec_1_1_6-3-g8e3daaf0b Thanks. 24 Aug 22:07:32 ntpd[6053]: NTSc: Strange ALPN returned: *ntske/1 (8) The "*" is fixing non graphic characters. -- These are my opinions. I hate spam. ___ devel mailing

Re: Interesting talk on Chronos

Mark Atwood : > On Sat, Aug 24, 2019, at 20:54, Eric S. Raymond wrote: > > Mark Atwood via devel : > > > > Interesting talk about changing the sampling algorithm to harden NTP > > > > against time-shift attacks. This is very much on-mission for us and I > > > > > > Any updates or thoughts? > > >

Re: Interesting talk on Chronos

On Sat, Aug 24, 2019, at 20:54, Eric S. Raymond wrote: > Mark Atwood via devel : > > > Interesting talk about changing the sampling algorithm to harden NTP > > > against time-shift attacks. This is very much on-mission for us and I > > > > Any updates or thoughts? > > Daniel seems to think it;s

Re: gitlab testing broken for Fedora

On Sat, Aug 24, 2019 at 02:42:08AM -0700, Hal Murray via devel wrote: > Stage: build > Name: fedora-rawhide-refclocks-gpsd > Trace: GPG Keys are configured as: > file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora- > 31-x86_64 > Public key for glibc-common-2.30.9000-1.fc32.x86_64.rpm is not installed. >

Re: Interesting talk on Chronos

Mark Atwood via devel : > On Sun, Jul 28, 2019, at 20:04, Eric S. Raymond via devel wrote: > > https://www.youtube.com/watch?v=2HVtswVGmak&list=PLC86T-6ZTP5j2xKSoqW0_ajvdr58Fau6g&index=6 > > > > Interesting talk about changing the sampling algorithm to harden NTP > > against time-shift attacks. Th

Re: ALPN checking

On Sun, Aug 25, 2019 at 4:46 AM Hal Murray via devel wrote: > The 3rd case is when it gets back something other than "ntske/1". > I haven't found a test case for that one yet. If anybody still has a > system > still running our old/buggy code, please let me know the IP Address. > Hal, 203.123.4

prep for point release of NTPSec, suggest 2019-07-31

There is discussion of a need for a point release of NTPsec. I agree, we've done a bunch of useful and user visible stuff. How does everyone feel about next Saturday, Aug 31 2019-07-31? That gives us a week to beat on our new features, and to merge and beat on pending merge requests. ..m M

Re: Interesting talk on Chronos

On Sun, Jul 28, 2019, at 20:04, Eric S. Raymond via devel wrote: > https://www.youtube.com/watch?v=2HVtswVGmak&list=PLC86T-6ZTP5j2xKSoqW0_ajvdr58Fau6g&index=6 > > Interesting talk about changing the sampling algorithm to harden NTP > against time-shift attacks. This is very much on-mission for us

ALPN checking

I just pushed the code for the NTS client to check the ALPN selection returned from the NTS server. It logs one of 3 messages. Here are samples of 2 of them: 24 Aug 13:18:38 ntpd[28519]: NTSc: No ALPN from spidey.rellim.com (TLSv1.2) 24 Aug 13:18:43 ntpd[28519]: NTSc: Good ALPN from: time.clo

Re: git head broken on NetBSD 7.2 - weird

On Fri, Aug 23, 2019 at 9:11 PM Hal Murray via devel wrote: > > > Has anybody seen anything like this before? > > Assuming "no", I'll try bisecting tomorrow. > > My attempt at bisecting hit a brick wall. I backed up many months and it > still fails. > > I guessed that something strange had happe

Re: Point release of NTPSec

Hal Murray : > > e...@thyrsus.com said: > > But doing the right thing is better than a switch. And the test is a cost > > that only needs to be paid once. > > I think your no-switch approach is good for things where the choice is A or > B, > like picking the right baud rate. > > But this isn

Re: _XOPEN_SOURCE in ntpd/refclock_gpsd.c => warnings on BSD

Hal Murray via devel writes: >> I see no changes related to _XOPEN_SOURCE since 2017. Perhaps you're >> thinking of GPSD, where there was bunch of rework in that area just before >> the 3.19 release. > > Thanks. You are probably right. > > Eric: This area just got more complicated. See #614 >

Re: Point release of NTPSec

Hal Murray via devel writes: >> Basically, I wish to highlight that things may *break* with pre 1.2.0 > > Do we have any hints that anybody else who interoperated with our old code > depended on our bug? Pretty much everybody seems to have had the same bug: accepting whatever the server sent bac

gitlab testing broken for Fedora

Stage: build Name: fedora-rawhide-refclocks-gpsd Trace: GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora- 31-x86_64 Public key for glibc-common-2.30.9000-1.fc32.x86_64.rpm is not installed. Failing package is: glibc-common-2.30.9000-1.fc32.x86_64 GPG Keys are configured as:

Re: Point release of NTPSec

I just changed the NTS key rotation timer from 1 hour to 1 day. The spec is setup for 1 day. 1 hour enables testing. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel