3 ms·
> Without addressing the thing about the NIST P-curves being backdoored, which is an extremely dubious proposition I don't believe it exactly either, I just kn
by WorldMaker 7y ago
> Without addressing the thing about the NIST P-curves being backdoored, which is an extremely dubious proposition
I don't believe it exactly either, I just know it as a zeitgeist reason why some of the dialog about curve changes has been happening. In hindsight I supposed I'd have been better off not mentioning it.
> Standards should immediately deprecate support for explicit curve parameters.
I agree and that wasn't the intent of my post, if it came across that way. While elsewhere in the thread it is mentioned that many named curves are implemented standalone, my understanding is that not all of them are.
I was only suggesting that crypto32.dll is intended to be low level enough that it is possible that some of the higher-level APIs that Microsoft has built that do focus on named curves only (such as the UWP/WinRT and .NET APIs I mentioned) may rely on the explicit parameter support in the lower level library. I don't envy Microsoft the task of balancing what is in a low-level API like that versus backwards compatibility, "upwards" compatibility with high level components, etc.