extra port nnnn, nts port nnnn

2024-04-14 Thread Hal Murray via devel
I just pushed code that optionally listens on a second port. The NTS-KE server will tell the client to use that port. Requests going out will be from the new port. The idea is to bypass ISP filtering on port 123. Testing encouraged. I've been testing with nts port 8123 Be sure to let

CI is broken

2024-04-14 Thread Hal Murray via devel
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.com/gitlab-or g/gitlab-runner/gitlab-runner-helper:x86_64-v16.11.0" with specified policies [always]: Error response from daemon: manifest for

Crappy testing

2024-04-14 Thread Hal Murray via devel
If you use the extra port stuff I pushed last night, port 123 stops working. Ugh, blush. I usually do better than that. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org