k...@roeckx.be said:
> Please use 0 instead of TLS_MAX_VERSION, it means the same. I've marked
> TLS_MAX_VERSION for deprecation.
Thanks for the heads up.
Is there any documentation on that? (man page?)
Is there a symbol for default or any version?
--
These are my opinions. I hate spam.
I think we need to change the names in the enum types in order to avoid
potential name collisions.
Things like AEAD_AES_128_GCM are likely to appear in OpenSSL and/or we are
likely to go looking for them there. There are actually 2 name spaces for
that sort of thing, 2 different enums. One
Screw it, it's worth it. I'm going to be at this.
..m
--
Mark Atwood
http://about.me/markatwood
+1-206-604-2198
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
| The CERT Coordination Center invites you to attend
| the CERT Vendor Meeting 2019. The meeting will
| be held on Monday March 4, 2019, at the Westin
| St. Francis in San Francisco, CA, US.
This is the sort of thing that does make me occationally wish I lived near
the SF Bay Area.
..m
--
Mark said:
> This sounds somewhat similar to the brilliant hack that is
> https://github.com/ioerror/tlsdate
Brilliant? Maybe if you do it for yourself. Not if you publish it in a way
that encourages others to do it.
I'm going to decide to not to decide right now. We leave those refclocks
in for now. This conversation is illuminating.
On Wed, Feb 6, 2019 at 9:32 AM Eric S. Raymond via devel
wrote:
> Richard Laager via devel :
> > I have (and was/am using) a clock using the Spectracom driver, with the
> >
This sounds somewhat similar to the brilliant hack that is
https://github.com/ioerror/tlsdate
On Wed, Feb 6, 2019 at 9:34 AM Eric S. Raymond via devel
wrote:
> Richard Laager via devel :
> > On 2/5/19 7:49 PM, Richard Laager wrote:
> > > I have a specific proposal that I'll hopefully write up
e...@thyrsus.com said:
>> That program would probably be handy for debugging so maybe we should write
>> it anyway.
> This sounds like you volunteering to write and test the code.
I added some ugly code to my hack client to generate a canned request, and
similar hackery in the server to
On Wed, Feb 06, 2019 at 02:05:27PM -0800, Hal Murray via devel wrote:
>
> float mintls = 1.2; /* minimum TLS version allowed */
> float maxtls; /* maximum TLS version allowed */
>
> Floats? The API to OpenSSL doesn't work in floats. We'll have to translate
>
float mintls = 1.2; /* minimum TLS version allowed */
float maxtls; /* maximum TLS version allowed */
Floats? The API to OpenSSL doesn't work in floats. We'll have to translate
those to something useful. I'd like to push that back to ntp_config.
>From
Richard Laager via devel :
> On 2/5/19 7:49 PM, Richard Laager wrote:
> > I have a specific proposal that I'll hopefully write up tonight, which
> > may address the needs in this space.
> I did some brainstorming on this with a colleague. I initially started
> with an approach that would consider
Richard Laager via devel :
> I have (and was/am using) a clock using the Spectracom driver, with the
> two-digit year. It recently suffered from GPS rollover, so I disabled
> the GPS source in ntpd. I'm using the PPS source with network sources
> (which I was using anyway) to number the seconds.
On 2/6/19 1:52 AM, Hal Murray wrote:
> You can also try fudging it by 1024*7*24*60*60
Sure, and we discussed that in the bug. I was just giving an algorithm
to deal with it automatically.
--
Richard
___
devel mailing list
devel@ntpsec.org
On 2/5/19 7:49 PM, Richard Laager wrote:
> I have a specific proposal that I'll hopefully write up tonight, which
> may address the needs in this space.
I did some brainstorming on this with a colleague. I initially started
with an approach that would consider the system clock (if after
14 matches
Mail list logo
