e...@thyrsus.com said:
> The peers display looks OK, so my test to see if a number should be inserted
> in the status field is probably busted. Should be trivial to fix once ntpd
> ships the right thing.
The peers display is often somewhat screwy. I suspect something in your
recent table cle
dfoxfra...@gmail.com said:
>> The K and I used to encrypt cookies is a hack constant so old
>> cookies work over server reboots.
> I assume this is temporary while you work on this code, right? Obviously if K
> is a hardcoded constant you have no security.
Right. Total hack to allow debugging
Hal Murray :
>
> The t column is a "u" for user/client. (Looks like "l" for refclocks. It
> used to be interesting for broadcast and such, but I think you can figure
> that
> out from the remote address.)
>
> We can put 0-8 in that slot to indicate that we are talking to that server
> with
On 2/20/19 7:26 AM, Hal Murray via devel wrote:
> For non public IP Addresses (aka behind a NAT box) you can use self signed
> certificates.
In that scenario, you can still use Let's Encrypt. Use the DNS challenge
method. The Let's Encrypt client (on the NTS-KE server) uses nsupdate
(or similar)
On Wed, Feb 20, 2019 at 12:48 AM Hal Murray via devel wrote:
> The K and I used to encrypt cookies is a hack constant so old cookies work
> over server reboots.
I assume this is temporary while you work on this code, right?
Obviously if K is a hardcoded constant you have no security.
> With the
> If I have a real certifucate, I don't know it.
You have one on any web server that supports https. I don't know where it
lives. Probably someplace in apache land.
Gary says it's easy to get them via Lets Encrypt. Their web page says you
need to control the domain. Gary said you only need a
Hal Murray :
> > Excellent. What's the bext thing you need from me?
>
> Testing. Get it up and running in your local environment. If you have a
> real
> certificate and are willing to support some testing traffic, tell me/us the
> host name and/or send us the root certificate.
If I have a r
This is from an old ntpq -p
The new ntpq is similar.
remoterefid st t when poll reach delay offset
jitter
===
=
0.0.0.0 .POOL. 16 p- 2560..
0.
