diff options
| -rw-r--r-- | PROTOCOL.u2f | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/PROTOCOL.u2f b/PROTOCOL.u2f index 066d09951..61b70d6ef 100644 --- a/PROTOCOL.u2f +++ b/PROTOCOL.u2f | |||
| @@ -37,7 +37,7 @@ hardware, thus requiring little on-device storage for an effectively | |||
| 37 | unlimited number of supported keys. This drives the requirement that | 37 | unlimited number of supported keys. This drives the requirement that |
| 38 | the key handle be supplied for each signature operation. U2F tokens | 38 | the key handle be supplied for each signature operation. U2F tokens |
| 39 | primarily use ECDSA signatures in the NIST-P256 field, though the FIDO2 | 39 | primarily use ECDSA signatures in the NIST-P256 field, though the FIDO2 |
| 40 | standard specified additional key types include one based on Ed25519. | 40 | standard specifies additional key types, including one based on Ed25519. |
| 41 | 41 | ||
| 42 | SSH U2F Key formats | 42 | SSH U2F Key formats |
| 43 | ------------------- | 43 | ------------------- |
| @@ -49,10 +49,6 @@ OpenSSH integrates U2F as new key and corresponding certificate types: | |||
| 49 | sk-ssh-ed25519@openssh.com | 49 | sk-ssh-ed25519@openssh.com |
| 50 | sk-ssh-ed25519-cert-v01@openssh.com | 50 | sk-ssh-ed25519-cert-v01@openssh.com |
| 51 | 51 | ||
| 52 | These key types are supported only for user authentication with the | ||
| 53 | "publickey" method. They are not used for host-based user authentication | ||
| 54 | or server host key authentication. | ||
| 55 | |||
| 56 | While each uses ecdsa-sha256-nistp256 as the underlying signature primitive, | 52 | While each uses ecdsa-sha256-nistp256 as the underlying signature primitive, |
| 57 | keys require extra information in the public and private keys, and in | 53 | keys require extra information in the public and private keys, and in |
| 58 | the signature object itself. As such they cannot be made compatible with | 54 | the signature object itself. As such they cannot be made compatible with |