On Thu, Apr 10, 2025 at 12:26:15PM -0700, Gary E. Miller via announce wrote:
> No comments? Everyone is good with a weekend release of NTPSec as is?
Hi Gary,
Sounds good to me. I'll do the release over the weekend unless I hear
otherwise.
Cheer
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.
What's the story on new waf install directories vs old waf directories?
Do we need to change the code and/or fix the documentation?
Is there anything else we need to sort out before a release?
--
These are my opinions. I hate spam.
___
specific?
> I suggest at least a week, maybe two week, quiet period for testing.
We've been talking about a release for a long time. I've been assuming
people have been testing.
--
These are my opinions. I hate spam.
___
devel
anything else we need to sort out before a release?
Only if you want to wait for the egg-info to wheel info change.
I would not wait on that change or sock reflcock.
Release it already. Gary? Matt? Anyone lurking in the rafters?
___
devel mail
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?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://l
Yo Hal!
On Wed, 02 Apr 2025 23:15:36 -0700
Hal Murray wrote:
> Gary said:
> >> We've been talking about a release for a long time. I've been
> >> assuming people have been testing.
> > I do not assume that. Likely they will test after release.
>
Gary said:
>> We've been talking about a release for a long time. I've been
>> assuming people have been testing.
> I do not assume that. Likely they will test after release.
By "people", I was thinking of those who read @devel.
I assume your "the
s not important...
> > Some I am not happy about.
>
> Anything specific?
Not tonight, maybe Tuesday. I saw some things fly by that I wanted to
check.
> > I suggest at least a week, maybe two week, quiet period for
> > testing.
>
> We've been talking about a rel
Yo Hal!
On Sun, 30 Mar 2025 15:16:36 -0700
Hal Murray via devel wrote:
> I think we are ready.
A lot of changes in the last few days. Some I am not happy about.
I suggest at least a week, maybe two week, quiet period for testing.
RGDS
GARY
I think we are ready.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
also propose that we only support the current version of any distro.
So if you want to install on an old system, you can use buildprep as a
guide, but you will have to do some work to sort out the details.
I just added a last-tested line to each mainline path.
The idea is to test what we
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
> Python 2.7 works with either version of waf.
Thanks.
Why are we keeping the old version?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/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
> 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?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lis
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
What needs to happen before we can get a release out?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
I think we are getting close. I'm shifting my efforts to testing.
Does anybody know of things that need fixing or merging or ??? before a
release?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
It would be really nice if we had a working example of a cross compile,
and something like a HOWTO-cross to document it, including the packages
that need to be installed.
It would be nice if option-tester could also do an install, bin-test, and
uninstall.
Best in a scratch directory.
--
T
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
What's the story on new waf vs old python?
https://gitlab.com/NTPsec/ntpsec/-/issues/830
--enable-pylib none needs work
https://gitlab.com/NTPsec/ntpsec/-/issues/819
Should that be --disable-python?
--
These are my opinions. I hate spam.
__
> 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 scanne
Things have been quiet recently. Is it time for a release?
Is there anything we should imiplement or fix before a release?
Has anybody scanned the bug/issue list recently?
--
These are my opinions. I hate spam.
___
devel mailing list
devel
On Wed, Dec 06, 2023 at 01:56:51AM +, Matthew Selsky via devel wrote:
> Sounds good. I'll aim to release ~15-Dec-2023.
Hi all,
Sorry for the delays. I have a release candidate tarball available:
https://ftp.ntpsec.org/pub/releases/ntpsec-1.2.3rc1.tar.gz
https://ftp.ntpsec.org/pub/
On Mon, 18 Dec 2023, Fred Wright wrote:
On Mon, 18 Dec 2023, Matthew Selsky wrote:
On Sun, Dec 17, 2023 at 08:17:23PM -0800, Fred Wright via devel wrote:
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
> 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?
On Sun, 17 Dec 2023, Hal Murray wrote:
Fred Wright said:
The main issue I've found is that the "struct var" in ntp_control.c, is
relying on anonymous unions, which are a relatively new language feature.
That is my attempt at getting a sane procedure for adding slots to the table.
The old sch
On Sun, Dec 17, 2023 at 08:17:23PM -0800, Fred Wright via devel wrote:
Hi Fred,
> The main issue I've found is that the "struct var" in ntp_control.c, is
> relying on anonymous unions, which are a relatively new language feature.
> They were originally a GNU extension, eventually becoming officia
c builds.
That seems worth fixing.
I don't think we should hold up the release unless somebody fixes it in the
next day or two.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
Fred Wright said:
> The main issue I've found is that the "struct var" in ntp_control.c, is
> relying on anonymous unions, which are a relatively new language feature.
That is my attempt at getting a sane procedure for adding slots to the table.
The old scheme required coordinated edits in sev
On Wed, 6 Dec 2023, Matthew Selsky via devel wrote:
Sounds good. I'll aim to release ~15-Dec-2023.
Fortunately this hasn't happened yet. :-)
The main issue I've found is that the "struct var" in ntp_control.c, is
relying on anonymous unions, which are a relati
I’ll create a release candidate on Monday 12/18 and then a final release
shortly thereafter.
Thanks,
-Matt
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
> I'll aim to release ~15-Dec-2023
Sounds good. Thanks.
> I'm thinking about AES becoming the new default for ntpq, etc.
I got a few a day or so ago. I missed that one. I'll get it tonight.
--
These are my opinions. I hate spam.
On Sat, Dec 02, 2023 at 08:09:00PM -0800, Hal Murray 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.
Hi Hal,
Sounds good
Yo Hal!
On Sun, 03 Dec 2023 17:44:45 -0800
Hal Murray via devel wrote:
> Gary said:
> > DO you have an account on: https://scan.coverity.com/
> > If so, I think I can add you to the project.
>
> How does their stuff work? How often do they check NTPsec?
> Or what should I be asking?
Ever
Gary said:
> DO you have an account on: https://scan.coverity.com/
> If so, I think I can add you to the project.
Thanks. I think i worked.
How does their stuff work? How often do they check NTPsec?
Or what should I be asking?
How much mail should I expect? ...
There are 3 Coverity quirk
Yo Hal!
On Sun, 03 Dec 2023 15:07:18 -0800
Hal Murray via devel wrote:
> > Gary said:
> > > Uh, not quite. Check the Coverity stuff.
> >
> > How do I do that?
>
> DO you have an account on: https://scan.coverity.com/
On further checking,halmurray...@sonic.net is an admin
on the
Yo Hal!
On Sun, 03 Dec 2023 15:07:18 -0800
Hal Murray via devel wrote:
> Gary said:
> > Uh, not quite. Check the Coverity stuff.
>
> How do I do that?
DO you have an account on: https://scan.coverity.com/
If so, I think I can add you to the project.
RGDS
GARY
-
Gary said:
> Uh, not quite. Check the Coverity stuff.
How do I do that?
I'd expect something to send me email but I don't remember anything about
Coverity.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://l
Yo James!
On Sat, 2 Dec 2023 21:12:04 -0800 (PST)
James Browning via devel wrote:
> 4. The buildbots are not reporting any unplanned regressions; there
> are always issues to be addressed.
Uh, not quite. Check the Coverity stuff.
RGDS
GARY
-
> 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
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.
--
These are my opinions. I hate spam.
___
devel ma
anywhere in
the release process documentation. Yes, PIVOT.h probably should be
updated. I had a scheme for when to update the pivot time; It does
not matter what it was.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/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
Is updating PIVOT.h on your checklist and/or should I update it now while I/we
think of it?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
> What sort of testing did you have in mind?
Nothing in particular. We haven't had a release in a while so I hope
everybody will run git head and keep an eye out for glitches, make sure their
favorite toys work as expected, double check log files, etc...
> Any specific doc cleanu
)
Here are the open issues the caught my eye:
https://gitlab.com/NTPsec/ntpsec/-/issues/806
https://gitlab.com/NTPsec/ntpsec/-/issues/802 (is this resolved with our latest
FIPS changes, and do we have an environment to test it?)
Do you think these or any others should delay the release
> 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 re
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 testing. And documentation checking/cleanup.
Does anybod
> 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 request
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 working on making a couple of new stats files for NTP packet
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
Hi all,
We had some recent commits to fix issues found by Google's OSS-Fuzz scanner so
we've decided to do a release candidate today and then a full release next week
after we've had some more time to kick the tires.
The release candidate is available at
https://ftp.ntpsec.o
> On 12/15/2022 1:21 PM PST Matthew Selsky via devel wrote:
>
>
> Hi all,
>
> I plan to cut a release on Thu 12/22/2022. I'm sorry about the delays in
> getting this release out the door.
>
> If there's anything that absolutely must be in this rel
Hi all,
I plan to cut a release on Thu 12/22/2022. I'm sorry about the delays in
getting this release out the door.
If there's anything that absolutely must be in this release and can't wait
until the next release, please let me know. Otherwise, I plan to tidy up the
NEWS fil
e offending feature in the two builders. I will add
> another merge request to allow the failure of the on-push macOS runners.
>
> Also, the last merge into the tree was in mid-August; Enough time has passed
> that a release can be made.
>
Given the general lack of commits to f
macOS runners.
Also, the last merge into the tree was in mid-August; Enough time has passed
that a release can be made.___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
On Apr 20, 2022 07:30, Matt Selsky via devel wrote:Hi Hal,
I'd like to get https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1264 merged and then do the release.
Is there anything else that we want in the release?Yes, but in the interest of helping get it out on this calendar the rest
I looked at 1268. I split it into a bunch of pieces and merged a bunch
of it. That shrinks the diff, making it easier to follow. Further
comments are on the MR.
On 5/2/22 09:35, countkase--- via devel wrote:
On Thursday, April 21, 2022, 09:20:06 AM PDT, Matt Selsky
wrote:
Hi James,
I'm no
On Thursday, April 21, 2022, 09:20:06 AM PDT, Matt Selsky
wrote:
> Hi James,
>
> I'm not sure if you're being serious or not with the "nah" :)
>
> The potential mac truncation seems serious. I'm not sure about the other 2
> issues.
>
> Let me know what you think.
1254 temporarily resolved th
[Mail to devel has about a 10 hour delay.]
Sorry for not providing more context on my first try.
> "nts nowildcards" changes the default from wildcards allowed to not allowed.
> server blah, blah "nowildcards" turns off wildcards for this slot
> server blah, blah "wildcardsOK" allows wildcards fo
> Sorry, I'm not following what you mean here. Do you have a patch or merge
> request that I can look at?
I should be able to explain it.
In the config file:
"nts nowildcards" changes the default from wildcards allowed to not allowed.
server blah, blah "nowildcards" turns off wildcards for t
On Fri, Apr 22, 2022 at 12:13:25AM -0700, Hal Murray via devel wrote:
> nts nowildcards at the top level to set the default
> nowildcards at the server level
> wildcardsOK at the server level to override the default
Hi Hal,
Sorry, I'm not following what you mean here. Do you have a patch or merg
Thanks again for your helpful comments.
On the cert documentation ...
What is our target audience? Admins who already know about certificates or
newbies who are getting a certificate for the first time? (This was my first.)
Is there a certificates-for-newbies document we can reference?
If not
On 4/22/22 02:08, Hal Murray wrote:
+1 to NOT making this a knob.
Would you please say more.
It would be invisible unless you go looking for it.
Are you against unnecessary knobs in general?
Yes.
If I had pushed this code a
month or 3 ago when we weren't discussing a release or wild
Richard Laager said:
> 8 cases? I thought it was one setting, which would be 2 cases.
> Can you expand upon what you're actually proposing? Ideally as a merge
> request, but at least explain the knobs here.
nts nowildcards at the top level to set the default
nowildcards at the server level
wild
> +1 to NOT making this a knob.
Would you please say more.
It would be invisible unless you go looking for it.
Are you against unnecessary knobs in general? If I had pushed this code a
month or 3 ago when we weren't discussing a release or wildcards, would you
have spoken up agains
On 4/21/22 03:17, Hal Murray via devel wrote:
There are 8 cases. I think I tested them all. If it will make you happy,
I'll test again, being careful to check all 8 cases.
8 cases? I thought it was one setting, which would be 2 cases.
Can you expand upon what you're actually proposing? Ideal
On Thursday, April 21, 2022, 09:20:06 AM PDT, Matt Selsky
wrote:
> Hi James,
>
> I'm not sure if you're being serious or not with the "nah" :)
>
> The potential mac truncation seems serious. I'm not sure about the other 2
> issues.
>
> Let me know what you think.
Serious on all three and hey s
Hi James,
I'm not sure if you're being serious or not with the "nah" :)
The potential mac truncation seems serious. I'm not sure about the other 2
issues.
Let me know what you think.
Thanks,
-Matt
___
devel mailing list
devel@ntpsec.org
https://lists
ess someone asks for this to be a knob.
Thanks,
-Matt
From: Hal Murray
Sent: Wednesday, April 20, 2022 2:12 PM
To: Matt Selsky
Cc: devel@ntpsec.org ; Hal Murray
Subject: Re: Getting ready for a release, wildcards
[The mail system is in sloth mode again.]
matthew
[Eric: There are a couple of preceding messages to devel in the mail
someplace.]
> I'd like to get https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1264 merged
> and then do the release.
> Is there anything else that we want in the release?
I'm sorry that we have gotten of
Richard Laager said:
> Sure, that's all true. But, I'm not sure why you felt the need to mention
> this. That is how everything works. In general, it's not even guaranteed
> that a TLS-speaking daemon knows its own (external) hostname. It obviously
> can't know what is in the client's trust stor
any other release blockers? If not, I'll update the NEWS for the user-facing/high impact changes and cut a release candidate.Inconsistent output formatting for 'ntpq sysstats'? Bytes output of test data in 'waf check -v'? Potent
> I would rather not add knobs unless someone asks for this to be a knob.
Nobody outside is ever going to ask for this knob. It's a grubby detail.
Only geeks know that the concept exists.
I want this knob so I/we can experiment.
--
These are my opinions. I hate spam.
___
On 4/19/22 17:01, Hal Murray via devel wrote:
One is to update the nts cert documentation to say
that it doesn't do any checking on the certificate.
- Present the certificate in _file_ as our certificate.
+ Present the certificate (chain) in _file_ as our certificate.
+ +
+ Note that there
From: Hal Murray
Sent: Wednesday, April 20, 2022 2:12 PM
To: Matt Selsky
Cc: devel@ntpsec.org ; Hal Murray
Subject: Re: Getting ready for a release, wildcards
[The mail system is in sloth mode again.]
matthew.sel...@twosigma.com said:
> I don't think we should have a knob for dis
[The mail system is in sloth mode again.]
matthew.sel...@twosigma.com said:
> I don't think we should have a knob for disabling wildcards. This is not the
> sort of knob that operators expect (what other software provides such a
> knob?) and we're just adding another code path to test.
I'll be in
Hi Hal,
I don't think we should have a knob for disabling wildcards. This is not the
sort of knob that operators expect (what other software provides such a knob?)
and we're just adding another code path to test.
Are there any other release blockers? If not, I'll update the NEW
Hi Hal,
I'd like to get https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1264 merged
and then do the release.
Is there anything else that we want in the release?
Thanks,
-Matt
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/ma
I just pushed 2 tweaks. One is to update the nts cert documentation to say
that it doesn't do any checking on the certificate.
The other is a hack patch to aes_siv.c to supress deprecated warnings from
OpenSSL 3.
Is anybody (else) using OpenSSL 3?
It's trivial on FreeBSD. Just install open
> Sigh. I should get up to speed onmn crypto and certificates. I doubt I can
> do it fast enough to be useful on this one, though.
Service Names in TLS
https://datatracker.ietf.org/doc/draft-ietf-uta-rfc6125bis/
It's 24 pages with the usual amount of boiler plate so only half of that is
ser
Yo All!
openssl 3.0.0 is becoming an issue. See:
https://gitlab.com/NTPsec/ntpsec/-/issues/734
We have been stolling towards a release, what do we need to get one
out with openssl 3.0?
RGDS
GARY
---
Gary E. Miller Rellim
On Feb 15, 2022 1:05 PM, Hal Murray via devel wrote:> How about a release at the end of February to give people time to wrap things up?
The group that started this would like it by the 24th.No, but there's always the next one. I do have lists though. I am not in a position to push
> How about a release at the end of February to give people time to wrap things
> up?
The group that started this would like it by the 24th.
A RC (Release Candidate) would be a placeholder. Have we ever done one?
--
These are my opinions. I hat
On Feb 13, 2022 10:42 PM, Hal Murray via devel wrote:> How about a release at the end of February to give people time to wrap things up?
Sounds good to me.
Who has what that needs wraping up?I have some stuff I think needs to be in:- simplified release machinery !1253 #603- mode 6 cli
> How about a release at the end of February to give people time to wrap things
> up?
Sounds good to me.
Who has what that needs wraping up?
Richard is working on the Trimble driver.
I need to take another look at the NMEA driver.
-
>> It's been almost a ye
Hi Hal,
How about a release at the end of February to give people time to wrap things
up?
Thanks,
-Matt
From: devel mailto:devel-boun...@ntpsec.org>> on
behalf of: Hal Murray via devel mailto:devel@ntpsec.org>>
Date: Monday, Feb 14, 2022, 01:24
To: Mark Atwood mailto:mark.atw..
It's been almost a year since 1.2.1
Debian is testing with OpenSSL 3.0
That's not supported in 1.2.1 but has been in git head for a while
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/ma
Where is your checklist for a release?
I've added PIVOT.h at the top level. It's only content is a #define for
RELEASE_DATE.
That's the magic constant that's needed for sanity checking and pivoting on
date conversions because using the build date would break repeatable b
My vote is to release, and I suspect other developers will mostly pass.
It would probably be nice if some developers could wander back.
huh, I have more commits recently than everyone else combined.
56 James Browning
15 Richard Laager
12 Matt Selsky
8 Hal Murray
3 Mark
The normative content of the RFC is not going to change. There's no
reason to hold back any release while waiting for publication.
On Fri, Sep 18, 2020 at 11:43 AM Hal Murray via devel wrote:
>
>
> Maybe we should get 1.2 out now/soon so it will be ready when the RFC comes
>
Maybe we should get 1.2 out now/soon so it will be ready when the RFC comes
out rather than shortly after.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
Hal Murray :
>
> > Looking at the changelog, the only one that jumps out at me is James's new
> > UI
> > options for ntpq.
>
> Should we have a policy of mentioning all UI changes?
I think so. I've been trying to do that whenever I write NEWS entries.
> How about config file changes?
Well,
> Looking at the changelog, the only one that jumps out at me is James's new UI
> options for ntpq.
Should we have a policy of mentioning all UI changes? I don't want a lot of
clutter, a quick mention should be enough to get people to check the
documentation.
How about config file changes?
On Fri, Sep 4, 2020 at 1:31 PM Hal Murray via devel wrote:
>
>
> Are any of the recent changes interesting enough to mention in NEWS?
Probably not so I'm just gonna empty the bucket. j/k
* duplicate server error message
* documentation updates/fixes
* shebang updates
* ntpkeygen can use secrets
*
wouldn't want to try doing anything deeper
this close to a release. None of it's user-visible.
After we ship I''ll get off my butt about the recvbuff cleanup.
--
http://www.catb.org/~esr/";>Eric S. Raymond
___
Are any of the recent changes interesting enough to mention in NEWS?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
Matthew Selsky :
> I also previously setup Codacy in order to see what other SAST systems could
> do. See https://app.codacy.com/gl/NTPsec/ntpsec/dashboard
>
> Let me know what you think. If either are useful, I'll integrate them more
> tightly in our workflows.
I'm already a fan of LGTM - it
1 - 100 of 354 matches
Mail list logo
