Lines Matching refs:signature

12 type as both the inputs to the signature operation and the resultant
13 signature differ from those specified for SSH. For similar reasons,
18 of "user presence" for each signature operation (typically achieved
21 given key is backed by hardware. Finally the signature format includes
22 a monotonic signature counter that can be used (at scale) to detect
38 the key handle be supplied for each signature operation. U2F tokens
59 While each uses ecdsa-sha256-nistp256 as the underlying signature primitive,
61 the signature object itself. As such they cannot be made compatible with
113 	string		signature key
114 	string		signature
131 	string		signature key
132 	string		signature
159 	string		enrollment signature
169 	string		enrollment signature
179 In addition to the message to be signed, the U2F signature operation
180 requires the key handle and a few additional parameters. The signature
193 The signature returned from U2F hardware takes the following format:
201 signature format used on the wire in SSH2_USERAUTH_REQUEST packets will
202 be reformatted to better match the existing signature encoding:
209 Where the "ecdsa_signature" field follows the RFC5656 ECDSA signature
215 For Ed25519 keys the signature is encoded as:
218 	string		signature
227 FIDO standards, but requires different signature contents to raw FIDO
229 "webauthn-sk-ecdsa-sha2-nistp256@openssh.com" signature algorithm.
232 signature is similar to the sk-ecdsa-sha2-nistp256@openssh.com format:
242 Where "origin" is the HTTP origin making the signature, "clientData" is
244 extensions used in making the signature.