# Documentation of FIDO2 supported crypto algorithms

**URL:** <https://support.nitrokey.com/t/documentation-of-fido2-supported-crypto-algorithms/2203>\
**Category:** Nitrokeys\
**Created:** [February 18, 2020, 9:29pm UTC](https://support.nitrokey.com/t/documentation-of-fido2-supported-crypto-algorithms/2203 "2020-02-18T21:29:20Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![szszszsz](https://support.nitrokey.com/letter_avatar_proxy/v4/letter/s/d07c76/32.png) [@szszszsz](https://support.nitrokey.com/u/szszszsz)\
**Post date:** [February 26, 2020, 8:31am UTC](https://support.nitrokey.com/t/documentation-of-fido2-supported-crypto-algorithms/2203/8 "2020-02-26T08:31:46Z")

</div>

> [@jan](#):
>
> But in context of FIDO2 this discussion is pointless because FIDO2 requires `secp256r1` and we can’t change that. Any other curve implemented in our device would be useless because it couldn’t be used with any application.

In other words, the algorithm has to be implemented as well on the server side, so the signature could be validated, otherwise it will be rejected. I do not know any FIDO2 compliant server implementation, which would support `curve25519`. In the linked documentation the identificators for known algorithms are listed.

Edit: It does not mean it is impossible to support it, but the API (ids, algorithms) has to be common between server (webservice) and client (device/browser) to make it work.

---

_[View the full topic](https://support.nitrokey.com/t/documentation-of-fido2-supported-crypto-algorithms/2203)._
