I've tracked down the problem, but don't know how to fix it.
NetBSD 7.2 has an optional newer version of OpenSSL. pkgin has installed it.
I didn't do that explicitly so I assume it was dragged in by something I did
install. Looks like python37-3.7.3nb1
waf is using the new headers.
On Sun, Aug 25, 2019 at 3:49 PM Hal Murray via devel
wrote:
> I think it should be fixed for the release, but I don't know how to do it.
>
> There used to be code in the msyslog processing that handled %m if it
> wasn't
> included in the local printf. I'm guessing it was removed to eliminate
>
I think it should be fixed for the release, but I don't know how to do it.
There used to be code in the msyslog processing that handled %m if it wasn't
included in the local printf. I'm guessing it was removed to eliminate
warnings on some systems that don't support %m.
All the %m cases were
On Sun, Aug 25, 2019 at 1:49 PM Achim Gratz via devel
wrote:
> Mark Atwood via devel writes:
> > How does everyone feel about next Saturday, Aug 31 2019-07-31?
>
> You've got a time machine? 8-)
>
No, but as Chronos is not implemented, he can set time to what ever he
wants on the NIST and
> Any updates or thoughts?
[I watched the talk but not all the Q]
I think our efforts would be much more productive helping to deploy NTS.
They are trying to protect against MitM attacks, but they assume that only
some of the servers can be attacked. That misses the important case where the
