Proposal to include additional cryptographic algorithms in the NTPSec implementation

[Hal Murray]

Sarath said:
> (Apologies for this duplicate mail... I am still trying to figure out
> this mailing list usage) 

One hint is that because of SPF, the From header gets mangled to:
  From: Sarath _Msft_ via devel <devel at ntpsec.org>
If you don't look carefully, that can easily look like a message you are 
working on will be sent to the sender rather than the list, especially if 
your mail reader is "helpful" and doesn't display the real email address 
inside the <>.



> I can give one more compelling reason for this proposal ...

I don't see that as compelling.

If it were simple, I probably would have done it already.

But it's not simple.  We don't directly use the OpenSSL AEAD routines.  We 
use a library with a simpler API.  (AEAD is a 2 pass algorithm.  OpenSSL 
needs to handle data that won't fit in memory so the 2 passes get exposed 
to the API.  Our data is tiny.  We get to use a simpler API.)

So until I see a better reason, this stays on the nice-to-have list.

If anybody else wants to work on this, I can steer you in the right 
direction.

------

Crazy idea department.

I know next to nothing about Windows.
I/we would like to get NTPsec running on Windows.
I think there is a pretty good POSIX environment for Windows.
  So most of the code should just work.

If you will help me get NTPsec working on Windows, I'll extend the AEAD 
colection that we support.


-- 
These are my opinions.  I hate spam.