3 ms·
If anyone has the time and skills to implement these curves in NSS, I'm sure that the Firefox and Chrome security teams would be more than happy to enable them!
by jvehent 12y ago
If anyone has the time and skills to implement these curves in NSS, I'm sure that the Firefox and Chrome security teams would be more than happy to enable them!
- sarciszewski 12y agohttps://bugzilla.mozilla.org/show_bug.cgi?id=957105 https://bugzilla.mozilla.org/show_bug.cgi?id=957105 Looks like there's already a bug in Mozilla's tracker.
- tptacek 12y agoVery smart crypto implementors are already working on this codebase, aren't they?
- jvehent 12y agoNot being one of them myself, I can only notice that their time is limited, and many much wanted improvements sit on the backburner waiting for a smart crypto implementor to work on them. NSS and OpenSSL are difficult codebases to work with, which may also explain why it's so hard to find people to work on them.
- higherpurpose 12y agoI'm not as worried about Chrome/Mozilla as I am about IE and Safari (including the mobile one).
- hsivonen 12y agoWhy do you expect Firefox and Chrome to take patches as opposed to saying that patches should wait for specs from the TLS WG which waits for the CFRG to bless something? The political problem is that unless there's an authority whose blessing can be appealed to to justify inclusion, how do you decline curves from Microsoft Research and so-called NUMS curves? (Of course, it's not like the CFRG is a politically spoyless authority...)