Re: Do we run on any systems that don't support Go? Rust?

2025-06-08 Thread James Browning via devel
On Saturday, June 7, 2025 7:19:40 PM Pacific Daylight Time Gary E. Miller via devel wrote: > Yo Hal! > > On Sat, 07 Jun 2025 13:47:25 -0700 :::anip::: > Depends on what you mean "support". Google has said they do not "support" > got for anything, except their internal projects. They seem to h

Re: Do we run on any systems that don't support Go? Rust?

2025-06-07 Thread James Browning via devel
On Saturday, June 7, 2025 1:47:25 PM Pacific Daylight Time Hal Murray via devel wrote: > Gary said: > > Yes. Many. The list supported by go 1.24.4 seams to be just [1]: - aix - dragonfly bsd - freebsd - illumos - linux - macos - ms windows - netbsd - openbsd - plan 9 - solaris While rust (night

Re: Hiding evil code in invisible unicode / MR 1435

2025-04-21 Thread James Browning via devel
On Saturday, April 19, 2025 1:14:13 AM Pacific Daylight Time Hal Murray via devel wrote: > > I saw a note recently about AI being susceptable to hiding evil code in > invisible unicode. > > New Vulnerability in GitHub Copilot and Cursor: How Hackers Can Weaponize > Code Agents > https://www.pi

Re: Hiding evil code in invisible unicode

2025-04-19 Thread James Browning via devel
> On 04/19/2025 1:14 AM PDT Hal Murray via devel wrote: > > We allow/require UTF-8 rather than simple ASCII. I know we need that to > get the character for micro, as in microseconds. Do we need it for > anything else? We should be able to get away with closer to ASCII, if we encode micro an

Re: Strangeness in 842 Fix

2025-04-14 Thread James Browning via devel
On Monday, April 14, 2025 3:16:46 PM Pacific Daylight Time Fred Wright via devel wrote: > I was just looking at recent changes, and came across commit 4756b6317. > I don't know anything specifically about the *_TIMESTAMPNS_OLD stuff, but > I do know that the SO_* symbols are for the socket options

Re: Release: waf vs install directories

2025-04-05 Thread James Browning via devel
On Wednesday, March 26, 2025 11:09:51 AM Pacific Daylight Time Hal Murray wrote: > If somebody is still using Python 2, do they have to manually fix the link > from waf to point to the old waf? Or is there some magic that takes care > of that? THERE IS NO MAGIC HERE, nor any fancy Python tricks.

Re: Starting ntpd as non-root

2025-04-05 Thread James Browning via devel
On Monday, March 17, 2025 4:52:25 PM Pacific Daylight Time Hal Murray via devel wrote: > Back in 2018, I did some work on getting ntpd to start as ntp:ntp > There was a way on Linux to set some capabilities on a file. > > Somebody talked me/us out of this. I don't remember why. > > I've poked a

Re: Release: waf vs install directories

2025-04-05 Thread James Browning via devel
On Monday, March 24, 2025 3:12:44 PM Pacific Daylight Time Hal Murray via devel wrote: > What's the story on new waf install directories vs old waf directories? The pylib/wscript has been changed so that the egg-info, and all .py files in pylib are installed in PYTHONDIR (see MR 1450) TLDR PYTH

Re: INSTALL.adoc

2025-04-04 Thread James Browning via devel
On Friday, April 4, 2025 1:39:04 PM Pacific Daylight Time Gary E. Miller via devel wrote: > Yo Hal! > > I just pushes some changes to README-PYTHON. > > I already found a mistake. Bonus points if anyone finds the > error... nstalled? no sist-packages? no potential mistaking dist-package for

Re: INSTALL.adoc

2025-04-04 Thread James Browning via devel
On Friday, April 4, 2025 1:39:04 PM Pacific Daylight Time Gary E. Miller via devel wrote: > Yo Hal! > > I just pushes some changes to README-PYTHON. > > I already found a mistake. Bonus points if anyone finds the > error... Is it that the backslashes don't work the way they do in markdown and

Re: ntpsec | Add config files for clang tooling and IDEs/editors. (!1435)

2025-04-04 Thread James Browning via devel
On Friday, April 4, 2025 12:20:59 PM Pacific Daylight Time Gary E. Miller wrote: > > EditorConfig works with emacas, vim, and other editors > > Not on vim. Needs to be enabled on emacs. Dunno about others. I would not know as I do not use either. > > indent_style = space > > I agree, but NT

Re: INSTALL.adoc

2025-04-01 Thread James Browning via devel
On Monday, March 31, 2025 8:52:30 PM Pacific Daylight Time Hal Murray via devel wrote: > > +Alternatively you can link your python3 to python. > > +`ln -s /usr/bin/python3 /usr/bin/python` > > That "to" looks backwards to me. I expect: > link python to your python3 Or, you could symlink "py

Re: Anybody using the old waf?

2025-03-30 Thread James Browning via devel
On Sunday, March 30, 2025 4:44:51 PM Pacific Daylight Time Fred Wright via devel wrote: > I'm not sure what you mean by "my patches", given that I've never > submitted any for this issue, though I'd suggested what such patches might > do. The patches you were probably going to write if I had no

Re: Anybody using the old waf?

2025-03-30 Thread James Browning via devel
On Sunday, March 30, 2025 5:00:57 PM Pacific Daylight Time Fred Wright via devel wrote: > Actually, to be fair, I didn't find a file actually called 'waf' in the > upstream repo, but I did find a 'wscript' shebanged to 'python', and > assumed that that was indicative. I assumed that 'waf-light'

Re: Anybody using the old waf?

2025-03-30 Thread James Browning via devel
On Sunday, March 30, 2025 4:20:12 PM Pacific Daylight Time Fred Wright via devel wrote: > I'd actually been assuming that the incorrect 'python3' shebang line was > from upstream. I hadn't realized that the upstream version correctly > shebangs it to 'python', and that the change to the incorrec

Re: Anybody using the old waf?

2025-03-29 Thread James Browning via devel
On Saturday, March 29, 2025 1:52:15 PM Pacific Daylight Time Fred Wright via devel wrote: > How many people care about signatures *and* don't trust the ntpsec > signature *and* worry about the waf signature? None, Probably. I'm trying to look beyond the shallow for once. > It seems to me that th

Re: buildprep on Debian

2025-03-29 Thread James Browning via devel
On Saturday, March 29, 2025 2:24:04 AM Pacific Daylight Time Hal Murray via devel wrote: > Somebody is adding that python-dev > > Ahh. I found this: > # Prerequisites for the client Python tools: python extensions > case $installer in > apt) > $install "python${PYVERS

Re: Anybody using the old waf?

2025-03-28 Thread James Browning via devel
On Thursday, March 27, 2025 9:29:33 PM Pacific Daylight Time Fred Wright via devel wrote: > On Fri, 28 Mar 2025, Matt Selsky wrote: > > On Thu, Mar 27, 2025 at 02:48:54PM -0700, Fred Wright via devel wrote: > >> I've confirmed that it works with Python 2.7, including building the > >> extension.

Re: Any systemd wizards?

2025-03-28 Thread James Browning via devel
On Friday, March 28, 2025 4:45:24 AM Pacific Daylight Time James Browning via devel wrote: > On Friday, March 28, 2025 3:11:39 AM Pacific Daylight Time Hal Murray via > devel > wrote: > > I've got a fresh Fedora install. ntpsec builds and installs, but systemd > > doe

Re: Any systemd wizards?

2025-03-28 Thread James Browning via devel
On Friday, March 28, 2025 3:11:39 AM Pacific Daylight Time Hal Murray via devel wrote: > I've got a fresh Fedora install. ntpsec builds and installs, but systemd > doesn't like the ntpd.service that got installed. It's the same as what > I'm using on other Fedora systems. > > Has anybody seen t

Re: Release: waf vs install directories

2025-03-26 Thread James Browning via devel
On Wednesday, March 26, 2025 12:25:34 PM Pacific Daylight Time Hal Murray wrote: > > Python 2.7 works with either version of waf. > > Thanks. > > Why are we keeping the old version? Paranoia, I figured that if I removed it there would be a high chance something would go wrong and I would be re

Re: Release: waf vs install directories

2025-03-25 Thread James Browning via devel
On Monday, March 24, 2025 8:25:10 PM Pacific Daylight Time you wrote: > > The code has changed, behavior is not noticeably different than it was > > before. > Didn't it change from dist-packages to site-packages on Debian and friends? Yes, it does due to upstream waf and/or Python changes. Accord

Re: new waf vs PYTHONDIR

2025-03-18 Thread James Browning via devel
On Tuesday, March 18, 2025 3:10:58 PM Pacific Daylight Time Gary E. Miller via devel wrote: > Yo James! :::snip::: > > And who or what changes the symlink? When? Why? Documented? The individual user who should not change the symlink probably will. They should never unless the waf-2.1.4 compa

Re: new waf vs PYTHONDIR

2025-03-18 Thread James Browning via devel
On Mar 18, 2025 13:44, Hal Murray via devel wrote:> I tried to bisect the git.  No luck.  The issue depends on which Python I> am running.commit e899c2ffd4243e933150f2349874e4e462657c54Author: James Browning Date:   Thu Mar 13 02:06:11 2025 -0700    Use waf 2.1.4, revise, and drop Py2.6 builds.Whi

Re: Modern languages

2025-03-18 Thread James Browning via devel
D and Java are supported and have waf 'Tools'. Rust and Golang do not have them. After revising devel/hacking.adoc, someone would need to write the tools. After that, we should start by rewriting pieces of libntp in Rust. Given the current pace, it will take a while. _

Fwd: Re: Man page formatting quirk

2025-03-14 Thread James Browning via devel
-30--- Forwarded message --From: James Browning Date: Mar 14, 2025 15:59Subject: Re: Man page formatting quirkTo: Hal Murray Cc: Inconvenient.On Mar 14, 2025 15:16, Hal Murray via devel wrote: I  a few RFCs to the ntpd man page. The code looks like this: RFC 8915::   D. Fra

Shout out

2025-03-13 Thread James Browning via devel
At various times, Hal Murray wrote: > If you have any python2 environments, please test, and give an extra scan > over the printout. I ran across two things when doing some testing. 1. On my Fedora 41 instance it fails w/ --enable-pylib=ext because of a bad Python 2.7 build 2. A Debian:oldold

Re: Release?

2025-03-12 Thread James Browning via devel
On 2025-03-11T21:58:07-0700, Hal Murray wrote: > What needs to happen before we can get a release out? 0. Someone should update the "devel/hacking.adoc" release process checklist, later. 1. It's past time to release; we have landed new features and significant bug fixes, and too many days have

Re: Thread priorities

2025-03-05 Thread James Browning via devel
On 2025-03-04T20:00:13-0800, Hal Murray via devel wrote: > Do we want to get a release out now or continue fixing/tweaking things? The Internet recommends releasing early and often to improve engagement; we do neither. === On 2025-03-04T20:55:06-0800, Matt Selsky via devel wrote: > - Are there

Re: Bug#1086000: ntpsec: ntpd runs with SCHED_FIFO 99 and might starve the system

2025-03-01 Thread James Browning via devel
> On 03/01/2025 6:06 AM PST Hal Murray via devel wrote: > I hope you/Debian don't have to maintain patches. They maintain some; I looked at the stack, and they are patches for clan Debian packages. I think Fedora does the same for RPM packaging. > ntpd only uses one thread. (more when doing DNS

Re: CI stuff failing

2025-02-17 Thread James Browning via devel
On Feb 16, 2025 23:36, Matt Selsky via devel wrote:On Sun, Feb 16, 2025 at 11:16:28PM -0800, Hal Murray via devel wrote: > I poked around a bit and didn't find anything with version numbers.  There > was a latest. asciidoc3.org's blog mentions a complete revamp of their website. See https:

Re: DeprecationWarning from waf

2025-02-16 Thread James Browning via devel
On Sunday, February 16, 2025 9:26:28 PM Pacific Standard Time Hal Murray via devel wrote: > What does this mean? Is it going to cause us any trouble? > > > /home/murray/ntpsec/raw/./waf:101: DeprecationWarning: Python 3.14 will, > by default, filter extracted tar archives and reject files or mo

clangd, black, editorconfig evangelism was: Is it time to --enable-warnings?

2025-02-13 Thread James Browning via devel
I assume that few people use clangd[1] much. With a reasonable config file, clangd can reach -Werror -Weverything. Clangd can also reformat code like clang-format[2]. Someone should translate the dot.emacs file into .clangd, .clang-format, and .editorconfig [3] files. While I am not inclined t

Re: https://ntpsec.org/downloads.html

2025-02-08 Thread James Browning via devel
On Feb 8, 2025 18:19, Hal Murray via devel wrote: > Though it's best to recommend forking and then cloning the fork, since > that's a more appropriate setup for submitting MRs. Thanks. It would be great if you could write a few words about that -- or add a URL to someplace that already

Re: https://ntpsec.org/downloads.html

2025-02-07 Thread James Browning via devel
On Friday, February 7, 2025 5:11:35 AM Pacific Standard Time Hal Murray via devel wrote: > Sigh. It needs a dose of TLC. I can make requests but I can not get them merged. > The Downloads section has 2 URLs. > The first one is https://gitlab.com/groups/NTPsec > git clone on that one doesn

Windows and other AEAD ciphers

2025-02-03 Thread James Browning via devel
Building on windows will cause pain in the neck. Microsoft's SDK coaster image is a gigabyte and a half compressed. However, after too much frustration, I got an unrelated toy program to build on Linux. Building NTPsec on Linux but for Windows would require us to either bring back or re-impleme

Re: Anybody still using Python2?

2025-02-02 Thread James Browning via devel
On Feb 2, 2025 05:54, ASSI via devel wrote:openSUSE Factory / tumbleweed just dropped python2 completely and thereis no system poython interpreter anymore (only python3).  How to tellstupid waf to not "#!/usr/bin/env python" every script?Probably the --pyshebang option of waf configure, or maybe -

Re: Glitch from ntpmon

2025-02-02 Thread James Browning via devel
> On 02/01/2025 4:45 PM PST Hal Murray via devel wrote: > > > I've seen this twice. > This is talking to a remote system that has (very) recently restarted ntpd. > > > Traceback (most recent call last): > File "/usr/local/bin/ntpmon", line 371, in > sl = statline(peer_report, mru_repor

Re: Fixing cross compile armhf tangle

2025-01-31 Thread James Browning via devel
> On 01/31/2025 12:59 AM PST Hal Murray via devel wrote: > > > Currently, our CI cross compile armhf case is failing. We discussed this > back in Sept and I fixed things by handling each of 5 cases individually. > It turns out there are more than 5 cases. I missed the others so that's > why cros

Re: Can't find ntpc on NetBSD

2025-01-30 Thread James Browning via devel
On Thursday, January 30, 2025 2:30:14 AM Pacific Standard Time Hal Murray via devel wrote: > I'm update/upgrading and cleaning up my NetBSD boxes. > > ntpmon broke. Python gave a backtrace rather than a simple error message. > > File "/usr/local/lib/python3.13/site-packages/ntp/ntpc.py", line

Re: Anybody still using Python2?

2025-01-29 Thread James Browning via devel
On Wednesday, January 29, 2025 1:53:08 PM Pacific Standard Time Matt Selsky via devel wrote: > Hi, > > Does the newer waf version drop 2.6 support? I'd be happy to drop all py2 > support in NTPsec, but I don't feel that strongly about it either way. The new waf requires a top-level sysconfig mo

Re: Checking issues (for a release)

2025-01-27 Thread James Browning via devel
On Monday, January 27, 2025 3:10:55 AM Pacific Standard Time Hal Murray via devel wrote: > What's the story on new waf vs old python? > https://gitlab.com/NTPsec/ntpsec/-/issues/830 Python versions before 2.6 break because they seem to lack an 'as' keyword. Python 2.6 fails on my system becaus

Re: Coverity check please...

2025-01-20 Thread James Browning via devel
On Monday, January 20, 2025 3:39:37 PM Pacific Standard Time Hal Murray via devel wrote: > > Still seems like a bug to me. Any potential UB is bad. Should be easy > > to work around. > > Please look at the code. It's only 10 lines. > > If you can suggest a fix, I'll try it. > (I already tried

Re: Coverity check please...

2025-01-19 Thread James Browning via devel
On Sunday, January 19, 2025 12:32:01 AM Pacific Standard Time Hal Murray via devel wrote: > I think it's a bug in Coverity. Would somebody please check. > > Is there a way to report bugs to Coverity? Or tell it not to check > something? It looks like one to me. I looked at the subject code and

Re: Storage leaks

2025-01-12 Thread James Browning via devel
On Sunday, January 12, 2025 2:56:50 PM Pacific Standard Time Hal Murray wrote: > James Browning said: > > I would be more concerned in the near and intermediate terms about the > > possibility of allocating memory to pointer that already have associated > > memory. > > Right. But one way to find

Re: Storage leaks

2025-01-12 Thread James Browning via devel
On Sunday, January 12, 2025 12:27:51 PM Pacific Standard Time Hal Murray via devel wrote: > Once upon a time, there was code that would free up most/all of the memory > that we had allocated when ntpd exited. So valgrind could be used to look > for storage leaks without having to wade through too

Re: Is free(NULL) OK?

2025-01-12 Thread James Browning via devel
On Saturday, January 11, 2025 10:43:47 PM Pacific Standard Time Hal Murray via devel wrote: > The Linux man page says >If ptr is NULL, no operation is performed. > > I'd expect a wrapper if there really was a problem. > > This code is in ntpd/ntp_config.c > if (NULL == s) {

Re: ftp.ntpsec.org folder for my stuff & malingering

2025-01-09 Thread James Browning via devel
On Monday, January 6, 2025, at 1:00:07 PM Pacific Standard Time, Gary E. Miller via devel wrote: > I want a unicorn. Why does "ftp" even exist any more? It is one of the machines in the NTPsec infrastructure. It serves the released tarballs, developer work files, and assorted miscellaneous fil

ftp.ntpsec.org folder for my stuff & malingering

2025-01-06 Thread James Browning via devel
I want a folder under 'ftp.ntpsec.org:users'. My public key with a couple line terminators instead of spaces is --- ssh-ed25519 C3NzaC1lZDI1NTE5IM/iIHgWIHnIhnA/gWECNKFJogB6h2ZL7K45d3LfVpWD jamesb@bourbon --- I intend to use it to stage unofficial releases like 1.2.3r1{,p2}, with the r1

Re: The server certificate for lists.ntpsec.org has expired again.

2025-01-03 Thread James Browning via devel
On Friday, January 3, 2025 1:50:54 PM Pacific Standard Time Gary E. Miller via devel wrote: > Yo Hal! > > On Thu, 02 Jan 2025 21:24:49 -0800 > > Hal Murray wrote: > > What other certs does ntpsec use? > > Mail server, the web site. I would think that the assorted websites need five certifica

The server certificate for lists.ntpsec.org has expired again.

2025-01-02 Thread James Browning via devel
I think a periodic soon before expiry check should be scheduled. ___ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel

Re: ntpsec | ntp_packetstamp: Fix possible time_t size mismatch. (!1414)

2024-12-24 Thread James Browning via devel
On Dec 24, 2024 15:21, Fred Wright via devel wrote:> I don't know what issue #832 is, but I don't see any "issues" link on the> project's GitLab page, making it hard to look up.Everyone is talking past each other; this is not good. It might be as bad as you not finding the second issue in the open

Re: Time for a new waf?

2024-12-22 Thread James Browning via devel
On Saturday, December 21, 2024 11:53:14 AM Pacific Standard Time Hal Murray via devel wrote: > Before the release? Great Ghu no. After the release. If only because at least two functions in wafhelpers/options _need_ to be reworked. Notably the glue setting (cross) C and LD FLAGS as well as comm

Re: Old OpenSSL Cpmpaitibility

2024-12-18 Thread James Browning via devel
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

Re: Time for a release?

2024-12-05 Thread James Browning via devel
> On 12/02/2024 11:07 AM PST Hal Murray via devel wrote: > > Things have been quiet recently. Is it time for a release? It probably is time for a release, and quiet is one word for it. > Is there anything we should imiplement or fix before a release? > Has anybody scanned the bug/issue list

re: CI: The "cross-build" job doesn't have EVP_MD_CTX_new

2024-09-07 Thread James Browning via devel
  On 09/07/2024 3:49 PM PDT Hal Murray via devel wrote:     I assume it's from this change: https://gitlab.com/NTPsec/ntpsec/-/commit/ 7c8b5fe20eafe911be4eac64467a032a52753313#887b5ad6972aa0

CI: The "cross-build" job doesn't have EVP_MD_CTX_new()

2024-09-07 Thread James Browning via devel
The Ubuntu 16 04 "cross-build" job is busted and I have no idea how to fix it. I thought one idea behind the "build-cross-armhf" job was that "cross-build" would have gone away. Will someone who may address this please do so? -30- signature.asc Description: This is a digitally signed message p

Re: sys_vars_list

2024-07-19 Thread James Browning via devel
On Friday, July 19, 2024 3:04:45 PM PDT Hal Murray via devel wrote: > > James Browning said: > > You should be able to run the following to get the list of variables > > (but no type info). > > > $ ntpq -c "rv 0 sys_vars_list" > > > which seem to not work for a while, > > I can't find any refe

Re: Strange error on NetBSD

2024-06-21 Thread James Browning via devel
On Friday, June 21, 2024 1:35:59 PM PDT Hal Murray via devel wrote: > Does anybody other than me run/test on NetBSD? I do not; I think I tested on NetBSD once or a few times years ago. > The test-all part of option-tester gets the following error. > > ntp_stdlib includes signal.h > Do we have to

Add ntpcert-sweep was "What next?"

2024-06-17 Thread James Browning via devel
I've created a handy script, "ntpcert-sweep.py," which can display the complete TLS certificate chain from a certificate PEM file or an NTS server to a root certificate file on the host machine. The timestamps are probably GMT, the hexstrings are X509v3 Subject and Authority Key Identifiers. Aft

Re: How old a version of OpenSSL do we support?

2024-06-11 Thread James Browning via devel
> On 06/11/2024 11:47 AM PDT Hal Murray via devel wrote: :::snip::: > So it looks like 1.1.0 isn't supported at all, much less older versions. > But if you aren't using NTS, we just need the crypto routines. So is > anybody running our code without NTS on really really really old versions > of O

Patch to make bin_test work without pylib

2024-04-25 Thread James Browning via devel
The clients needing it are still beinginstalled. I have another patch for that later.-30- 0003-Make-waf-bin_test-work-with-enable-pylib-none.patch Description: Binary data ___ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/

Re: Removing md5 usage from ntpsec

2024-04-17 Thread James Browning via devel
> On 04/16/2024 2:34 AM PDT Shreenidhi Shedi via devel wrote: > > Hi All, > > Currently ntpsec systemd service doesn't start if openssl fips is enabled. > The same issue was there in ntp as well. > > Looks like ntp is ready with the fix. More info at: > https://bugs.ntp.org/show_bug.cgi?id=3753

Re: Hack for monitoring NTP servers

2024-04-15 Thread James Browning via devel
> On 04/11/2024 12:39 PM PDT Hal Murray via devel wrote: > > > If somebody feels like hacking, something like this should be fun. > > The idea is to setup a ntpd server watching the servers you want to monitor. > (noselect on the server line does that) > > The new code is a program that wat

Re: CI is broken

2024-04-15 Thread James Browning via devel
> On 04/15/2024 9:15 AM PDT Matt Selsky via devel wrote: > > On Sun, Apr 14, 2024 at 01:30:47AM -0700, Hal Murray via devel wrote: > > I just pushed some code. The CI stuff sent me a Failed pipeline message. > > > > > > [0K[31;1mERROR: Job failed: failed to pull image > > "registry.gitlab.co

Re: What next?

2024-03-18 Thread James Browning via devel
On 03/17/2024 at 2:00 PM PDT, Hal Murray via devel wrote: > > Is anybody thinking about what we should be doing? > > > Here is my list: > > Port to Windows > Does anybody know anything about Windows? > Is there a decent POSIX environment? > How well does waf work on Windows? > We can get the m

RE: Addressing the Python 2, AsciiDoc classic, and AsciiDoc 3 tangle

2024-01-11 Thread James Browning via devel
> On 01/10/2024 7:49 PM PST Matt Selsky via devel wrote: > > Does anyone have links handy to statements from the various projects > on their long-term support status? Not as such. Hitting hub.docker.com I find no Python:2.6* images, Python:2.7* last pushed 21 April 2020, and Centos last pushed

Addressing the Python 2, AsciiDoc classic, and AsciiDoc 3 tangle

2024-01-07 Thread James Browning via devel
I suggest that Asciidoc3 should be dropped as it is not well-supported anywhere else and incurs additional maintenance costs. To address the support of AsciiDoc classic, we can use a Debian Bullseye image until around July/August 2024, as it has AsciiDoc classic. The current Debian Bookworm, which

Re: Release

2023-12-18 Thread James Browning via devel
> On 12/17/2023 9:49 PM PST Hal Murray via devel wrote: > > Fred Wright said: :::snip::: > > There are also a bunch of warnings with some compilers, which might be > > worth > > looking at. They're often fairly easy to fix, and sometimes indicate actual > > problems. > > Which compilers?

Re: Missing clockwork

2023-12-18 Thread James Browning via devel
> On 12/17/2023 11:49 PM PST Hal Murray via devel wrote: > > > Anybody recognize this? I've seen a missing file once before. I think it > was > clockwork.?? > > It works if I try it again. It sounds like a race condition in our wscript files or waf. How willing are you to sink time into t

Re: What does gitlab's "Successful pipeline" mean?

2023-12-06 Thread James Browning via devel
On Dec 5, 2023 23:45, Hal Murray via devel wrote: Does that mean no warnings? No errors slipped past any nets in their way.If not, how are we expected to learn about code that generates warnings on obscure systems?Maybe we should add -Werror or such to CFLAGS. The most obscure system tested i

Re: How does the parser work?

2023-12-04 Thread James Browning via devel
On Dec 4, 2023 13:49, James Browning wrote:The host phase of Waf build generates tablegen which in turn generates keywords.h IIRC. I have no idea how the internals work. I seem to recall that tablegen.c was badly scored by Codacy.Oops, keyword-gen and a rated; I need to get my memory replaced.

Re: How does the parser work?

2023-12-04 Thread James Browning via devel
On Dec 3, 2023 23:45, Hal Murray via devel wrote: ntp_parser.y contqains: %token     T_Tinker %token     T_Tlsciphers %token     T_Tlsciphersuites I'd expect those tokens to come from the keywords header file. But tlsciphers isn't in the keyword list. tlscipehrswuites is in

Re: Asciidoc question

2023-12-03 Thread James Browning via devel
On Dec 3, 2023 18:49, Hal Murray via devel wrote:What does the $$ after the +aga+ do? |+year+    |One generation file element is generated per year.     The filename  suffix consists of a dot and a 4 digit year number. |+age+$$   |This type of file generation sets changes

Re: Release

2023-12-02 Thread James Browning via devel
> On 12/02/2023 8:09 PM PST Hal Murray via devel wrote: > > > I think you should release what we have as soon as it is convenient. > > There are many more things I would like to include but we aren't making much > progress so it's time to do it. Referring to the first four items on the relea

Re: I/we need a lesson in git and/or gitlab and/or merge requests

2023-11-11 Thread James Browning via devel
Hal Murray wrote: > > Merge requests seem reasonable if all goes well. My work flow is roughly: > download the patch (URL plus ".patch") > scan it > maybe apply and test > approve and merge Ah, my work turbulence is incompatible with your workflow. > But things go downhill if I don't li

Re: Time for a release?

2023-11-05 Thread James Browning via devel
> On 10/31/2023 2:56 AM PDT Hal Murray via devel wrote: > > Is updating PIVOT.h on your checklist and/or should I update it now while > I/we > think of it? I do not see a reply on list; I will now bleat pointlessly. Updating PIVOT.h is not as far as I can tell mentioned anywhere in the releas

Re: Time for a release?

2023-10-31 Thread James Browning via devel
> On 10/31/2023 2:28 AM PDT Hal Murray via devel wrote: > > > Here are the open issues the caught my eye: > > https://gitlab.com/NTPsec/ntpsec/-/issues/806 > > I think we should fix that. Or at least try. It sounds like a bug in > ntp_control. I just tried rv xxx for some xxx that was a reas

Re: Time for a release?

2023-10-30 Thread James Browning via devel
> On 10/29/2023 10:50 PM PDT Hal Murray via devel wrote: > > The last time this was suggested, I encouraged waiting until we fixed mssntp. > Well, I think we have it fixed but we haven't found anybody to test it. > > So I think it's time to get ready for a release. > > Time for lots of testin

Re: Too many merge requests

2023-10-15 Thread James Browning via devel
> On 10/14/2023 7:16 PM PDT Hal Murray wrote: > > > James said: > > MR 1333 should address the issue where every response in an > > mssntp-restricted > > subnet gets lost in ntp_signd. > > Is there any reason to approve it now when we don't know if it works yet? I have tested it a bit; It pr

Too many merge requests

2023-10-14 Thread James Browning via devel
I currently have eight merge requests open; I would like other people to merge two. MR 1333 should address the issue where every response in an mssntp-restricted subnet gets lost in ntp_signd. MR 1331 addresses several issues with ntpdig and MAC handling. OTOH, I am still preparing MRs 1340, 1337,

Re: mssntp option breaking time service: tester(s) wanted

2023-10-04 Thread James Browning via devel
> On 10/04/2023 3:41 PM PDT Hal Murray wrote: > > > Does anybody have details on how MSSNTP signing works? > > If we can find that, we can write some POSIX code to test things. I have test tools that should push the right buttons IF I can get the correct magic number in the key ID. After runni

mssntp option breaking time service: tester(s) wanted

2023-10-04 Thread James Browning via devel
James Browning wrote: I have a patch series for ntpsec, which fixes time service for unauthed NTP traffic. It should also work on NTS. I have yet to test it there, though. I do not have a test rig for MS-SNTP. I would appreciate it if anyone could test it against MS-SNTP. Attaching a pcap

Re: I just pushed ntsstats and ntskestats

2023-09-27 Thread James Browning via devel
> On 09/26/2023 10:09 PM PDT Hal Murray wrote: > > > After glancing at the tops and bottoms fo some of the HTML docs, I think I > > have some issues to correct. > > I think the last line of the man pages used to have the version number. I'm > not seeing that now. > > Is that because I'm doing

Re: I just pushed ntsstats and ntskestats

2023-09-26 Thread James Browning via devel
> On 09/24/2023 6:09 PM PDT Hal Murray via devel wrote: > > > There was a request for ntpviz to show NTS traffic. We now have the log > files > to make that possible. That's good, I had some ntpviz glue that works with a different way of doing that. I'll check if I can graft it to work with

Re: I just pushed ntsstats and ntskestats

2023-09-25 Thread James Browning via devel
On Sep 24, 2023, 18:09, Hal Murray via devel wrote: There was a request for ntpviz to show NTS traffic.  We now have the log files to make that possible. Any documentation wizards?I am willing to break out some instant expert credentials on this until someone better shows up.Please look at t

Re: Tangle with -4 and -6

2023-09-19 Thread James Browning via devel
> On 09/17/2023 at 10:36 PM PDT, Hal Murray wrote: > > -4 and -6 work on the server line in ntp.conf but are not documented The closest I can see to an implementation is in ntpd/ntp_parser.y lines 390-395. I infer this to mean that it sets the Address Family of peer->srcaddr to a matching value.

Re: Is python2 dead?

2023-09-12 Thread James Browning via devel
> On 09/12/2023 12:00 AM PDT Hal Murray via devel wrote: > > > Gary said: > > Please, no. Go is a garbage collected language. Just what NTPsec does not > > need, random, unpredictable delays. It would appear there is a way to turn off GC under runtime/, Given this, it might be reasonable to

Re: Is python2 dead?

2023-09-04 Thread James Browning via devel
On Sep 4, 2023 14:46, Matthew Selsky via devel wrote:On Mon, Sep 04, 2023 at 02:25:46PM -0700, Gary E. Miller via devel wrote: > From RHEL: > > "The RHEL 8 AppStream Lifecycle Page puts the end date of RHEL 8's > Python 2.7 package at June 2024." > > https://access.redhat.com/solutions/4

Re: nts and ntske log files

2023-08-28 Thread James Browning via devel
On Aug 28, 2023 18:10, James Browning wrote:On Aug 28, 2023 17:10, Hal Murray wrote: James Browning said: > The NTP solution would be to convert the mess to l_fp which > will work for a bit less than 13 years. Thanks.  l_fp is the right answer. How did you get 13 years?  I get 136.  Did

Re: nts and ntske log files

2023-08-28 Thread James Browning via devel
> On 08/28/2023 3:08 PM PDT Hal Murray via devel wrote: > > > I just pushed the first cut. > > No documentation yet. > > Like sysstats and usestats, ntsstats and ntskestats get logged every hour. > > If you look at the output from ntpq -c nts, the counters fall into two > clumps, > one for

Re: Release, project sleeping, and running down the clock.

2023-08-22 Thread James Browning via devel
> On 08/22/2023 3:29 AM PDT Hal Murray wrote: > > > James Browning said: > > If the project is sleeping, then you may as > >well cut the new release now. > > I think we should do a normal release. That includes scanning the issues and > merge requests. And lots of testing. > > I'm work

Re: What does bison do with undefined tokens?

2023-08-22 Thread James Browning via devel
> On 08/22/2023 12:09 AM PDT Hal Murray via devel wrote: > > > ntpd/ntp_parser.y has this line: > > %token T_Timingstats > > T_Timingstats is never defined. All the other similar tokens are defined in > ntpd/keyword-gen.c I think that is a stub definition. It gets written int

Release, project sleeping, and running down the clock.

2023-08-21 Thread James Browning via devel
If the project is sleeping, then you may aswell cut the new release now. Otherwise I wouldappreciate it if people commented on my mergerequests 1331, 1333, and 1335. My other mergerequests 1335, 1330, and 1324 can wait a while.It is coming up on 8 months since 1.2.2 wasreleased.

outstadning? (non-)issues

2023-08-14 Thread James Browning via devel
- ms-sntp is broken - turning ms-sntp on breaks all time service - ms-sntp is blocking on every packet - IPv6 address to refid is broken with FIPS 140-2 - byte strings lack .hostname and .trusted in ntpdig - in ntp.packet, many hashes are not truncated to 20 bytes - when running ntpdig against a na

Re: NTPsec 1.2.2a released

2023-08-04 Thread James Browning via devel
> On 08/04/2023 6:35 PM PDT Fred Wright via devel wrote: > :::snip::: > > I notice that the two commits for that don't seem to be in any branch. > Having commits only "owned" by a tag and not a branch seems fragile. I do not think it is particularly fragile; I mean the garbage collector is tha

Re: [Git][NTPsec/ntpsec][master] 3 commits: Minor cleanups to restrict

2023-07-06 Thread James Browning via devel
On Jul 5, 2023 22:36, Matthew Selsky via devel wrote:Has this fix been submitted upstream to https://github.com/ThrowTheSwitch/UnityIt has now. https://github.com/ThrowTheSwitch/Unity/pull/680 ___ devel mailing list devel@ntpsec.org https://lists.ntpsec.

CI oops in the option testers

2023-06-22 Thread James Browning via devel
The Alpine Linux and Gentoo weekly option testers are not correctly failing on missing Python 2. Also, the CentOS and Fedora runners seem to be missing pkg-config packages. I have a possible partial workaround as !1327___ devel mailing list devel@ntpsec

Re: Warnings from unity

2023-06-21 Thread James Browning via devel
On Jun 21, 2023, 12:54, Hal Murray via devel wrote:> That usually means there is no "default:" case in a switch. OK, but where did the unity code come from and/or have we cloned it or are we tracking what they do?  Or ...I think it occasionally gets updated from GitHub [1].[1] https://github.

Re: master broken on macos

2023-04-13 Thread James Browning via devel
> On 04/13/2023 11:57 AM PDT Hal Murray via devel wrote: > > > I merged James' latest version for printing out the OpenSSL version during > configure. > > It barfs on macos. > https://gitlab.com/NTPsec/ntpsec/-/jobs/4105995926#L126 > > > The log file says: > > Checking for OpenSSL != 1.1.1a

  1   2   3   4   >