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
If you don't look carefully, that can easily look like a message you are
working on
While I understand you might be looking for buy-in before expending the
effort, one idea for moving this forward would be for you/Microsoft to
write a patch implementing this. Speaking in generalities and not to
this specific issue, it's a lot easier to accept something if there's a
clean patch
Thank you for your response. I am not a cryptography expert either - so perhaps
crypto experts even from Microsoft may have a different take on this.
>The RFC does specifically say that "Server implementations... MUST support
>AEAD_AES_SIV_CMAC_256." (RFC 8915, section 4.1.
This is a requiremen
On 2025-01-24 18:30, Sarath _Msft_ via devel wrote:
I am a software engineer with Microsoft Corporation.
I'm not a crypto expert nor am I speaking on behalf of the NTPsec
project, so take this with an appropriately sized grain of salt. ;)
As I understand it, the current NTPSec implementatio
