I think we should step back and look at the big picture.
Eric started working on the bits but got sidetracked on some cleanups.
I think we need to think hard about how/where/when we do the byte swapping.
More in another message. This isn't specific to NTS, but NTS is the first
time we have
On 1/30/19 5:14 PM, Gary E. Miller via devel wrote:
> On Wed, 30 Jan 2019 16:59:28 -0600
> Richard Laager via devel wrote:
>
>> There's another complication too. The server can send back a name or
>> an IP address. What happens if the client request contains a name and
>> the server's response
Gary said:
> The ntpsec ebuild for Gentoo installs multiple python modules. I wonder if
> this recent change broke that?
I don't remember any recent changes in the install area.
The change was to add version checking. It has pointed out a real problem
with separate locations for python2 and
Gary said:
> I installed for Python 2.7, then I installed for Python 3.6. Then I ran with
> python3.6, but my PYTHONPAATH was still for 2.7.
Do typical installations run mixed python 2 and 3 like that, or is that only
used for testing?
---
I think the mixed case can be made to work
Yo James!
On Wed, 30 Jan 2019 17:29:24 -0800
James Browning via devel wrote:
> On 1/30/19, Gary E. Miller via devel wrote:
> > Yo James!
> >
> > On Wed, 30 Jan 2019 14:57:15 -0800
> > James Browning via devel wrote:
> >
> >> as of commit 88430fb7d1 "raise SystemExit(1) on version mismatch"
On 1/30/19, Gary E. Miller via devel wrote:
> Yo James!
>
> On Wed, 30 Jan 2019 14:57:15 -0800
> James Browning via devel wrote:
>
>> as of commit 88430fb7d1 "raise SystemExit(1) on version mismatch" this
>> is what happens when you have multiple versions of pylib/ installed
>> and only one
Yo James!
On Wed, 30 Jan 2019 14:57:15 -0800
James Browning via devel wrote:
> as of commit 88430fb7d1 "raise SystemExit(1) on version mismatch" this
> is what happens when you have multiple versions of pylib/ installed
> and only one version of ntpclients/.
OK, but I'm not sure why you
Yo Hal!
On Wed, 30 Jan 2019 14:00:35 -0800
Hal Murray wrote:
> Gary said:
> > Great, the python library mismatch code works:
> > Library/Binary version mismatch
> > Binary: ntpsec-1.1.3+ 2019-01-30T21:25:37Z (git rev ab0ea27cf)
> > Library: ntpsec-1.1.3+ 2019-01-30T21:20:27Z (git
Yo Richard!
On Wed, 30 Jan 2019 16:59:28 -0600
Richard Laager via devel wrote:
> There's another complication too. The server can send back a name or
> an IP address. What happens if the client request contains a name and
> the server's response contains an IP? That might be a match (e.g. if
>
On 1/30/19 2:37 PM, Gary E. Miller via devel wrote:
> Sure there is, we now have a choice that did not formerly exist, and I
> can see uses for both:
>
> 1. If we do not get desired server: fail
> 2. If we do not get desired server: use the offered one instead
>
> #2 is new to NTS.
>
> For an
On 1/30/19, Hal Murray via devel wrote:
>
> Gary said:
>> Great, the python library mismatch code works:
>> Library/Binary version mismatch
>> Binary: ntpsec-1.1.3+ 2019-01-30T21:25:37Z (git rev ab0ea27cf)
>> Library: ntpsec-1.1.3+ 2019-01-30T21:20:27Z (git rev ab0ea27cf)
>
> What did
On 1/30/19 2:32 PM, Achim Gratz via devel wrote:
> Again, leave server for plain NTP and use a new keyword.
Perhaps you already did and I missed it, but can you explain why we need
a new top-level keyword rather than an option?
What is your config proposal for handling pools? Note that the
Gary said:
> Great, the python library mismatch code works:
> Library/Binary version mismatch
> Binary: ntpsec-1.1.3+ 2019-01-30T21:25:37Z (git rev ab0ea27cf)
> Library: ntpsec-1.1.3+ 2019-01-30T21:20:27Z (git rev ab0ea27cf)
What did you do to get that?
The version strings come
Yo Fred!
On Wed, 30 Jan 2019 13:41:27 -0800 (PST)
Fred Wright via devel wrote:
> On Tue, 29 Jan 2019, Gary E. Miller via devel wrote:
> > On Tue, 29 Jan 2019 19:01:40 -0800 (PST)
> > Fred Wright via devel wrote:
> >
> >>> Well, the way we use sys.stdout is warned about in the Python doc.
>
Yo All!
Great, the python library mismatch code works:
Library/Binary version mismatch
Binary: ntpsec-1.1.3+ 2019-01-30T21:25:37Z (git rev ab0ea27cf)
Library: ntpsec-1.1.3+ 2019-01-30T21:20:27Z (git rev ab0ea27cf)
Maybe it should not be a fatal error?
And is it a library, a module,
On Tue, 29 Jan 2019, Gary E. Miller via devel wrote:
On Tue, 29 Jan 2019 19:01:40 -0800 (PST)
Fred Wright via devel wrote:
Well, the way we use sys.stdout is warned about in the Python doc.
That is enough for me to want it aligned with the python doc.
The real question is why the build
Yo Richard!
On Wed, 30 Jan 2019 15:25:47 -0600
Richard Laager via devel wrote:
> On 1/30/19 1:41 PM, Gary E. Miller via devel wrote:
> > On Wed, 30 Jan 2019 01:19:08 -0600
> > Richard Laager via devel wrote:
> >
> >> So in this example, you have ntp.example.com as the NTS-KE server,
> >>
Yo Hal!
On Wed, 30 Jan 2019 12:52:13 -0800
Hal Murray wrote:
> >> Also, Python 3.6.7 on FreeBSD
> > Context? Is that a pass or a fail?
>
> Fail. Somebody was looking for a test case.
Good, more data points.
> It (and the previous one on NetBSD) both work from my normal script
> which
On 1/30/19 1:41 PM, Gary E. Miller via devel wrote:
> On Wed, 30 Jan 2019 01:19:08 -0600
> Richard Laager via devel wrote:
>
>> So in this example, you have ntp.example.com as the NTS-KE server, and
>> 1.2.3.4 or bob.example.com as the NTP servers? I assume it has to be
>> that way, as TLS
>> Also, Python 3.6.7 on FreeBSD
> Context? Is that a pass or a fail?
Fail. Somebody was looking for a test case.
It (and the previous one on NetBSD) both work from my normal script which
tee-s the output to a log file. Both fail when ssh-ed to that box and run
./waf without the tee.
Yo Hal!
On Tue, 29 Jan 2019 22:13:33 -0800
Hal Murray wrote:
> Gary said:
> >> https://secure-web.cisco.com/...
> > That is NOT the link I sent! Someone's email is messing with links!
> > Why would something called "secure-web" be doing non-secure
> > things???
>
> It's not uncommon for
Yo Achim!
On Wed, 30 Jan 2019 21:32:57 +0100
Achim Gratz via devel wrote:
> Gary E. Miller via devel writes:
> > I can see value in this for testing, but IMHO it should be
> > discouraged for general use. I'd like the new ntp.conf syntax to
> > somehow emphasize that this is discouraged and
Gary E. Miller via devel writes:
> I can see value in this for testing, but IMHO it should be discouraged
> for general use. I'd like the new ntp.conf syntax to somehow emphasize
> that this is discouraged and optional.
No. There are several institutions that have multiple servers of which
the
Yo Hal!
On Tue, 29 Jan 2019 23:13:18 -0800
Hal Murray via devel wrote:
> Also, Python 3.6.7 on FreeBSD
Context? Is that a pass or a fail?
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR
Yo Achim!
On Wed, 30 Jan 2019 20:44:31 +0100
Achim Gratz via devel wrote:
> Hal Murray via devel writes:
> >> I'd suggest using a new keyword for that and leaving the existing
> >> ones behijnd for NTP w/o encryption.
> >
> > Then we'll need 2 new keywords. We want NTS to work on pool sites
Yo Richard!
On Wed, 30 Jan 2019 01:18:38 -0600
Richard Laager via devel wrote:
> On 1/29/19 6:11 PM, Gary E. Miller via devel wrote:
> > Which conflicts with the Proposed RFC which says the NTS-KE tells us
> > which NTPD server, not the config file.
>
> The draft supports a mechanism wherein
Hal Murray via devel writes:
>> I'd suggest using a new keyword for that and leaving the existing ones
>> behijnd for NTP w/o encryption.
>
> Then we'll need 2 new keywords. We want NTS to work on pool sites too.
No, the client doesn't need to do anything special for pool servers
anymore, since
Yo Richard!
On Wed, 30 Jan 2019 01:19:08 -0600
Richard Laager via devel wrote:
> So in this example, you have ntp.example.com as the NTS-KE server, and
> 1.2.3.4 or bob.example.com as the NTP servers? I assume it has to be
> that way, as TLS doesn't work _in practice_ (yes, I know it is
>
28 matches
Mail list logo
