Re: Rough edge to clean up

2017-01-30 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > > There are three uses in libntp/macencrypt.c. Two of them are MAC > > computations that do require crypto security. You found the third, which > > doesn't. The flag seems to be intended to tag hashes that don't require > >

Re: Policy question - drop low-precision clocks?

2017-01-30 Thread Hal Murray
> The driver is polled, so it's not going to be shipping time at a fixed > offset from top of second. Reading the code, do you see any way we get > precision of less than a second out of it? It also gets normal serial info via true_receive The polling is necessary to handle the case where the

Re: Clocks broken on Mac mini

2017-01-30 Thread Hal Murray
> 30 Jan 19:46:40 ntpd[3773]: frequency error 2712 PPM exceeds tolerance 500 PPM > clock : 1416.61MHz If the clock really is 1.42 GHz but the system thinks it is 1.416... My calculations say it's off by 2400 ppm That's the sort of glitch I've been looking for. The next question is

Re: Clocks broken on Mac mini

2017-01-30 Thread Hal Murray
>From a second system: 30 Jan 19:46:40 ntpd[3773]: frequency error 2712 PPM exceeds tolerance 500 PPM 30 Jan 19:46:43 ntpd[3773]: ntpd exiting on signal 15 (Terminated) $ more /proc/cpuinfo processor : 0 cpu : 7447A, altivec supported clock : 1416.61MHz revision

Re: Clocks broken on Mac mini

2017-01-30 Thread Hal Murray
> $ uname -a Linux deb-ppc.example.com 3.16.0-4-powerpc #1 Debian 3.16.39-1 (2016-12-30) ppc GNU/Linux > $ cat /etc/issue Debian GNU/Linux 8 \n \l > One other query if I may - I think you've already confirmed this behaviour > across a couple of physical machines ? Just want to rule out a

Re: Clocks broken on Mac mini

2017-01-30 Thread Hugh Blemings
Hi Hal, All, Starting the day here :) On 31/01/2017 05:53, Hal Murray wrote: $ cat /proc/cmdline root=UUID=48d99649-90b2-4dc6-be05-5ca3858579a1 ro h...@blemings.org said: That sounds right for getting into OpenFirware - but for what we're digging into you shouldn't need to putz with it.

Re: Timings for random

2017-01-30 Thread Gary E. Miller
Yo Hal! On Sun, 29 Jan 2017 17:15:05 -0800 Hal Murray wrote: > g...@rellim.com said: > > You can't run out of randomness with RAND_bytes(). > > Would you please say more. The man page says: > >RAND_bytes() puts num cryptographically strong pseudo-random >

Re: Copyright dates

2017-01-30 Thread Mark Atwood
I will sweep through the documentation files, and add the correct forms and content for the copyright and license markings. ..m On Mon, Jan 30, 2017 at 12:02 PM Gary E. Miller wrote: > Yo Mark! > > On Mon, 30 Jan 2017 18:58:55 + > Mark Atwood

Re: Copyright dates

2017-01-30 Thread Gary E. Miller
Yo Mark! On Mon, 30 Jan 2017 18:58:55 + Mark Atwood wrote: > When you create a new file, mark it as follows (updating the year) as > required: [...] Can you add this advice to some doc that is in tree? RGDS GARY

Re: Copyright dates

2017-01-30 Thread Mark Atwood
Oh god, yeah. Stack Overflow copypastes are a constant headache today when doing due diligence when acquiring tech companies. Lots of people have been begging Stack Overflow to do something about it. The CC license that SO defaults all it's content to is not compatible with any open source or

Re: Copyright dates

2017-01-30 Thread Daniel Poirot
What's fun is hearing "No copyright needed, I got it off Stack Overflow!" ...wrong > On Jan 30, 2017, at 12:58 PM, Mark Atwood wrote: > > Commercial FOSS audit tools like Protecode and Blackduck will be able to > recognize the SPDX tags, and the Copyright text. > >

Re: Crypto timings

2017-01-30 Thread Kurt Roeckx
On Sun, Jan 29, 2017 at 10:44:49PM +0100, Kurt Roeckx wrote: > On Sun, Jan 29, 2017 at 09:09:56PM +, Greg Rubin wrote: > > Mind running the timings with the legacy interfaces as well? We may > > determine that the speed benefits are outweighed by the risks and > > complexities of an older

Re: Clocks broken on Mac mini

2017-01-30 Thread Hal Murray
> $ cat /proc/cmdline root=UUID=48d99649-90b2-4dc6-be05-5ca3858579a1 ro h...@blemings.org said: > That sounds right for getting into OpenFirware - but for what we're digging > into you shouldn't need to putz with it. It looks like the kernel code is getting the clock frequency from Open

Re: Clocks broken on Mac mini

2017-01-30 Thread Hal Murray
> That Mac Mini (Late 2005) was sold with either 1.3GHz or 1.5GHz, per > Mactracker. > Looks like you do have the 1.5GHz version. That doesn't agree with my samples in hand. There is a row of text on the underside along the connector edge. I have 3 samples: One gives serial number and

Re: Copyright dates

2017-01-30 Thread Daniel Poirot
Commercial FOSS audit tools like Protecode and BlackDuck will match a snippet and attribute to the FOSS project. > On Jan 30, 2017, at 12:30 PM, Mark Atwood wrote: > > That's... complicated. > > We don't need to have a notice attached to every file, because there is

Re: Copyright dates

2017-01-30 Thread Mark Atwood
That's... complicated. We don't need to have a notice attached to every file, because there is a copyright notice attached to the project as a whole, and there is a notice attached to each repo. Individual files generally don't each need their own notice, since individual files generally no

Re: Clocks broken on Mac mini

2017-01-30 Thread Frank Nicholas
That Mac Mini (Late 2005) was sold with either 1.3GHz or 1.5GHz, per Mactracker. Looks like you do have the 1.5GHz version. Frank Nicholas > On Jan 30, 2017, at 7:47 AM, Hal Murray wrote: > > > Ahhh goodies from syslog: > Jan 30 04:30:44 deb-ppc kernel: [

Re: Rough edge to clean up

2017-01-30 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > > Maybe not. I went looking for other places the refid computation is done > > and that seems to be it. What other other places did you have in mind? > > I was thinking of other places that called EVP_DigestInit > > If we

Re: Rough edge to clean up

2017-01-30 Thread Hal Murray
e...@thyrsus.com said: > Maybe not. I went looking for other places the refid computation is done > and that seems to be it. What other other places did you have in mind? I was thinking of other places that called EVP_DigestInit If we need that flag for addr2refid, do we need it for other

Re: Clocks broken on Mac mini

2017-01-30 Thread Hal Murray
h...@blemings.org said: > That sounds right for getting into OpenFirware - but for what we're digging > into you shouldn't need to putz with it. I got into open firmware. It doesn't like my KVM switching setup. A real keyboard worked. I did a printenv and didn't see anything clock related.

Re: Rough edge to clean up

2017-01-30 Thread Eric S. Raymond
Hal Murray : > > EVP_MD_CTX_FLAG_NON_FIPS_ALLOW is only used in libntp/macencrypt.c > > EVP_MD_CTX_init(); > #ifdef EVP_MD_CTX_FLAG_NON_FIPS_ALLOW > /* MD5 is not used as a crypto hash here. */ > EVP_MD_CTX_set_flags(,

Re: Policy question - drop low-precision clocks?

2017-01-30 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > > So, the only way to get accurate time out of this box is to pass its 1PPS > > output through an outboard conter chip. > > That doesn't make sense. If you have PPS, why not feed it into the serial > port. I don't know, man,

Re: Clocks broken on Mac mini

2017-01-30 Thread Hugh Blemings
Hi Hal, On 30/01/2017 22:45, Hal Murray wrote: h...@blemings.org said: If it would be of help I've a couple of friends who still do Linux/PowerPC kernel work, might be able to prod them about a fix at least for upstream if we have a simple to demonstrate test case and are confident it's in

Re: Recent trends in the codebase size

2017-01-30 Thread Hal Murray
fallenpega...@gmail.com said: > My inclination is that when more clock types show up, they get a driver > running in it's own process space, and exporting a SHM buffer. We should clean up the SHM interface first. The ntpd side should be read only. > The problem with covering existing drivers

Re: Clocks broken on Mac mini

2017-01-30 Thread Hal Murray
h...@blemings.org said: > If it would be of help I've a couple of friends who still do Linux/PowerPC > kernel work, might be able to prod them about a fix at least for upstream > if we have a simple to demonstrate test case and are confident it's in the > kernel. Thanks. I think that would

Re: Clocks broken on Mac mini

2017-01-30 Thread Hugh Blemings
Hiya, On 30/01/2017 19:56, Mark Atwood wrote: Hello Hugh, No need to be off list, we like to work in public as much as possible. Cool cool, works for me :) Yes, please make those connections, and prod your friends on this issue. No worries - by copy Hal - I apologise if I missed it but

Re: Copyright dates

2017-01-30 Thread Hal Murray
fallenpega...@gmail.com said: > Right now our standard copyright text is "Copyright $YEAR_YOU_ARE_WRITING_THI > S by the NTP Project contributors" Should the documentation files have a copyright notice? -- These are my opinions. I hate spam.

Rough edge to clean up

2017-01-30 Thread Hal Murray
EVP_MD_CTX_FLAG_NON_FIPS_ALLOW is only used in libntp/macencrypt.c EVP_MD_CTX_init(); #ifdef EVP_MD_CTX_FLAG_NON_FIPS_ALLOW /* MD5 is not used as a crypto hash here. */ EVP_MD_CTX_set_flags(, EVP_MD_CTX_FLAG_NON_FIPS_ALLOW); #endif if (!EVP_DigestInit_ex(,

Re: Policy question - drop low-precision clocks?

2017-01-30 Thread Hal Murray
e...@thyrsus.com said: > So, the only way to get accurate time out of this box is to pass its 1PPS > output through an outboard conter chip. That doesn't make sense. If you have PPS, why not feed it into the serial port. -- These are my opinions. I hate spam.

Re: Clocks broken on Mac mini

2017-01-30 Thread Mark Atwood
Hello Hugh, No need to be off list, we like to work in public as much as possible. Yes, please make those connections, and prod your friends on this issue. ..m On Mon, Jan 30, 2017 at 12:37 AM Hugh Blemings wrote: > Hiya, > > /me de-lurks > > On 30/01/2017 19:28, Eric S.

Re: Clocks broken on Mac mini

2017-01-30 Thread Hugh Blemings
Hiya, /me de-lurks On 30/01/2017 19:28, Eric S. Raymond wrote: Hal Murray : e...@thyrsus.com said: Well, that's disturbing. But hard to act on until we get a better idea what's busted Sorry if I wasn't clear. It's the kernel, not our code. Alas. Those would

Re: Policy question - drop low-precision clocks?

2017-01-30 Thread Hal Murray
e...@thyrsus.com said: > In the wake of the dumbclock removal, I'm now wondering if it makes any > sense at all to retain refclocks that report only in-band time to a > precision of a second. That is, without 1PPS. I think you are on a wild goose chase. You can get very accurate timing from a

Re: Clocks broken on Mac mini

2017-01-30 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > > Well, that's disturbing. But hard to act on until we get a better idea > > what's busted > > Sorry if I wasn't clear. It's the kernel, not our code. Alas. Those would have made nifty little test machines othwerwise. --

Re: Crypto timings

2017-01-30 Thread Eric S. Raymond
Hal Murray : > > e...@thyrsus.com said: > [context is cleaning up crypto code] > > Oh dear Goddess you are right. I think I noticed that before but spaced it. > > I'll fix that up once I've had some sleep. > > My straw man is that the table that holds keys has >