• Natanael
    link
    fedilink
    English
    4
    edit-2
    11 months ago

    I run a cryptography forum, I know this stuff, and the problem isn’t algorithmic weakness but complexity of implementation.

    All major browsers and similar networking libraries now have safe implementations after experts have taken great care to handle the edge cases.

    It’s not a fault with let’s encrypt. If they allowed nonstandard curves then almost nothing would be compatible with it, even the libraries which technically have the code for it because anything not in the TLS spec is disabled.

    https://security.stackexchange.com/questions/42088/can-custom-elliptic-curves-be-used-in-common-tls-implementations

    https://cabforum.org/baseline-requirements-certificate-contents/

    CAB is the consortium of Certificate Authorities (TLS x509 certificate issuers)

    With that said curve25519 is on its way into the standards

      • Natanael
        link
        fedilink
        English
        211 months ago

        P256 isn’t known to be insecure if implemented right, it’s just harder to implement right

      • Fluke McHappenstance
        link
        fedilink
        English
        111 months ago

        The WRC deals with unsafe curves all the time. I think picking a couple of spots on some of their curves at high speed would be interesting. Samir has been known to break some of these…