Add ES512 support

[Xuanwo]

Hi,

databendlabs/databend#5062 needs ES512 support from jsonwebtoken.

Is there anything special to take care of? I'm willing to submit a PR to add ES512 support 🚀

[a1ien]

First you need add P-512 to ring briansmith/ring#824

[s-frei]

This would be a great improvement 🙂

[deepu105]

Seems like there is an active PR to add support for this in ring. briansmith/ring#1631

[sscarduzio]

Please add ES512, we are blocked too

[Keats]

I think it will be available after #410

[arsenin-kitsoft]

@Keats ES512 is still needed, #410 is closed. Is there any help needed to push this?

[arsenin-kitsoft]

Working on a patch (investigating the lack of sign_recoverable in p-521 impl).

[arsenin-kitsoft]

@Keats So, I've added tests for ES512 and tested my fork against my application and it now works. Please merge the PR if everything is okay (there's some wonky custom DER conversions and signer/verifier workarounds, so please tell if I need to do better with them).

[Keats]

I've linked to the wrong one >_> #452

AFAIK, if we want to add another alg we need to do #480 so it's available for all providers but that's a breaking change

[arsenin-kitsoft]

I understand that #480 is a nice to have for the future, but I don't understand how is it neccesary to apply my patch that just adds a p521 package that has interface very close to existing p384 and the like.

Can we merge ES512 support now and refactor Result<> interfaces for #480 later?

[arckoor]

The main point of #480 is the #[non_exhaustive] on the Algorithm enum, which you also adjust in your PR. This will break third party providers, e.g. jsonwebtoken-botan. That said, the botan backed one is the only one I'm aware of, and it isn't even released on crates.io (because it's waiting on a botan release), so I'm personally fine with breaking it for the time being.

[arsenin-kitsoft]

I couldn't rebase over the interface changes, so I recreated the changes.