On Wed, 18 Dec 2024, Hal Murray wrote:
Fred Wright said:
I'm always in favor of maximum compatibility.
There is a tradeoff between broader compatibility and clutter in the code.
Indeed, though a good design keeps aspects dependent on the OS or other
outside packages well-segregated.
On Sun, 22 Dec 2024, Hal Murray wrote:
The macro to map EVP_MD_CTX_reset to EVP_MD_CTX_init wouldn't have
worked, but it didn't matter since that function isn't actually used. I
didn't think it was a good idea to leave a time bomb for some possible
future use, so I fixed it.
I would just
On Fri, 20 Dec 2024, Hal Murray wrote:
Pleae try again.
Looks like I had the #define backwards.
I copied that code from new defs which was trying to adapt to old code.
We want old defs to reverse adapt to new code.
I should have noticed that, but I was in the middle of doing three things
Pleae try again.
Looks like I had the #define backwards.
I copied that code from new defs which was trying to adapt to old code.
We want old defs to reverse adapt to new code.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@nt
On Thu, 19 Dec 2024, Hal Murray wrote:
Fix pushed. Please give it a try.
Not there yet. Sample from Fedora 25:
=
[219/265] Compiling libntp/pymodule-mac.c
In file included from ../../libntp/pymodule-mac.c:16:0:
../../i
Fix pushed. Please give it a try.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
Fred Wright said:
> Ubuntu 22
> Ubuntu 14
> Debian 7
> FreeBSD 10.3
> OpenBSD 5.6
> NetBSD 6.1.5
That's a good collection. Lots of museum bait.
> I'm always in favor of maximum compatibility.
There is a tradeoff between broader compatibility and clutter in the code.
This case is clean enou
On Wed, 18 Dec 2024, Hal Murray wrote:
It used to be possible to build with --disable-nts when a sufficiently
new OpenSSL wasn't available, but commit 7c8b5fe20 broke that. I'm not
sure why cryptographic functions are needed at all with --disable-nts,
but even if they are, the compatibility d
> I think the standalone MD5 and SHA code is long gone.
Yes, but it's in git someplace. It won't be that hard to find if we
really want it. I don't want to go there, but don't want to hide options
either in case somebody thinks it is important.
> I would be nice to move the control interfa
On Wednesday, December 18, 2024 1:03:16 AM Pacific Standard Time Hal Murray via
devel wrote:
> Do we have an official support policy? I'm expecting something like "runs
> on supported versions of most Unix like OSes with ntp_adjtime". Should we
> add "using supported versions of OpenSSL"?
deve
> It used to be possible to build with --disable-nts when a sufficiently
> new OpenSSL wasn't available, but commit 7c8b5fe20 broke that. I'm not
> sure why cryptographic functions are needed at all with --disable-nts,
> but even if they are, the compatibility definitions could have been in a
>
It used to be possible to build with --disable-nts when a sufficiently new
OpenSSL wasn't available, but commit 7c8b5fe20 broke that. I'm not sure
why cryptographic functions are needed at all with --disable-nts, but even
if they are, the compatibility definitions could have been in a single
12 matches
Mail list logo
