Re: recurring "standup"

2016-02-05 Thread Mark Atwood
Sounds good. On Fri, Feb 5, 2016, 10:13 PM Hal Murray wrote: > > fallenpega...@gmail.com said: > > Tweaking ntpq to show the setup is interesting. Is ntpq called by > anything > > of note in any of the main distributions. It may be worth adding that to > > the display in a way that doesnt chan

Re: recurring "standup"

2016-02-05 Thread Hal Murray
fallenpega...@gmail.com said: > Tweaking ntpq to show the setup is interesting. Is ntpq called by anything > of note in any of the main distributions. It may be worth adding that to > the display in a way that doesnt change too much, and then wait for bug > reports from distros and users. ntpq

Re: recurring "standup"

2016-02-04 Thread Eric S. Raymond
Hal Murray : > I may have blundered into a bug in ntpd's startup logic. I think it's > stepping the time when the first server responds rather than waiting to hear > from a few more servers. I also suspect this to be the case. I have a bit set to look into it, if you don't fix it first. --

Re: recurring "standup"

2016-02-04 Thread Mark Atwood
We should hold off still on adding or changing crypto for a while still. Tweaking ntpq to show the setup is interesting. Is ntpq called by anything of note in any of the main distributions. It may be worth adding that to the display in a way that doesnt change too much, and then wait for bug rep

Re: recurring "standup"

2016-02-04 Thread Hal Murray
fallenpega...@gmail.com said: > What have you all worked on in the past couple of weeks, what successes and > frustrations have you had, and what do you see yourself working on over this > next week? I've been poking around with shared key crypto and various ways of getting connected to a serve

Re: recurring "standup"

2016-02-03 Thread Hal Murray
v...@darkbeer.org said: > * Modify build system and rewind it back to the initial NTPSec commit -- > this is a WIP no ETA. What does that mean? It sounds interesting. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.o

Re: recurring "standup"

2016-02-03 Thread Mark Atwood
Hello Amar: Let me help sort that priority list: Get already existing OSes running on the new cloud provider. Check into GitLab repos all of the configuration files and slave build scripts for BuildBot.  It’s ok if they have to be non-public-readable repos for right now. Get cross compilation

Re: recurring "standup"

2016-02-03 Thread Amar Takhar
Sorry for the late response tried to organise a little and procmail threw this into the wrong folder. I'm currently working on and will still be working on: * Expanding workers under Buildbot - The old operating systems are back up just need to be enabled. I'm waiting for this unti

RE: recurring "standup"

2016-02-02 Thread Dan Poirot
...and in other news: http://www.csoonline.com/article/3027681/security/cisco-patches-authentication-denial-of-service-ntp-flaws-in-many-products.html Cisco Systems has released a new batch of security patches this week for flaws affecting a wide range of products, including for a criti

Re: recurring "standup"

2016-02-01 Thread Mark Atwood
Thank you Eric. For my own piece of mind, if you are not doing so already, please keep that private development branch of  the testframe work regularly pushed to a remote on gitlab.  It’s ok if it’s in a private branch under your personal account there. ..m On February 1, 2016 at 3:29:32 PM, E

Re: recurring "standup"

2016-02-01 Thread Eric S. Raymond
Mark Atwood : > Hello everyone (and hello from AU, I am in Geelong this week for #lca2016). > > What have you all worked on in the past couple of weeks, what successes and > frustrations have you had, and what do you see yourself working on over > this next week? Successes: 1. I've gotten back t