On Mon, Aug 19, 2019 at 7:22 AM Eric S. Raymond via devel
wrote:
> Hal Murray :
> > I remember a comment about there being no way to do broadcast securely.
> It
> > would be good to include an expanded version of that in the
> documentation.
>
> That's covered. In the page on NTPsec changes:
>
>
On Mon, Aug 19, 2019 at 1:45 PM Hal Murray via devel
wrote:
>
> There is probably something like a FAQ entry that explains that if you
> want to
> get time relevant data from A to B, you have to start by sending something
> from B to A, a nonce if nothing else.
>
> You could eliminate duplicates
> I was not sure if broadcast as a server was dropped for similar reasons.
The text for broadcast and multicast are not in the keyword generating file.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.
Yo All!
I just pushed Dan Drown's patch for the ALPN. That allows NTPsec to
interoperate with other NTS implementations.
But, it will break existing NTPsec NTS. So upgrade to git head now if
you use NTS.
For some reason GitLab has not allowed me to merge from their web pages
for a few weeks.
On 8/19/19 8:33 PM, Gary E. Miller via devel wrote:
> I just pushed Dan Drown's patch for the ALPN. That allows NTPsec to
> interoperate with other NTS implementations.
>
> But, it will break existing NTPsec NTS. So upgrade to git head now if
> you use NTS.
Can we get a point release soon, plea
On Mon, Aug 19, 2019 at 06:33:52PM -0700, Gary E. Miller via devel wrote:
> For some reason GitLab has not allowed me to merge from their web pages
> for a few weeks. I have to merge manually...
Hi Gary,
Sounds like you ran into https://gitlab.com/gitlab-org/gitlab-ee/issues/12686
I'm not sure
Yo Matthew!
On Tue, 20 Aug 2019 01:42:50 +
Matthew Selsky wrote:
> On Mon, Aug 19, 2019 at 06:33:52PM -0700, Gary E. Miller via devel
> wrote:
>
> > For some reason GitLab has not allowed me to merge from their web
> > pages for a few weeks. I have to merge manually...
>
> Sounds like y
On Mon, Aug 19, 2019 at 6:49 PM Gary E. Miller via devel
wrote:
> Yo Matthew!
>
> On Tue, 20 Aug 2019 01:42:50 +
> Matthew Selsky wrote:
>
> > I'm not sure why Dan's fork of the repo doesn't have jobs enabled...
>
> Every MR I have looked at on gpsd and ntpsec.
>
I am not a member of gpsd/g
Forgive my ignorance here, but - what does the stylized 'X' in the subject
line signify? I've only run across it here on the ntpsec list and the gpsd
list...
On 8/19/2019 18:49 PM, Gary E. Miller via devel wrote:
Yo Matthew!
On Tue, 20 Aug 2019 01:42:50 +
Matthew Selsky wrote:
On Mon,
Yo Paul!
On Mon, 19 Aug 2019 20:03:06 -0700
Paul Theodoropoulos via devel wrote:
> Forgive my ignorance here, but - what does the stylized 'X' in the
> subject line signify?
It only means that I set the original subject.
I started doing it to make it easier for me to see threads that I
started
> But, it will break existing NTPsec NTS. So upgrade to git head now if you
> use NTS.
What's the nature of the breakage?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/d
11 matches
Mail list logo