Skip to content

Commit 8033ce8

Browse files
shjalaeriknordmark
authored andcommitted
Explicitly mention signature format
Explicitly mention signatureHash format in the document. Signed-off-by: Shahriyar Jalayeri <[email protected]>
1 parent aadc6a1 commit 8033ce8

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

OBJECT-SIGNING.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,8 @@ The `AuthContainer` wrapper is constructed by:
3434

3535
1. Put the above payload in the `protectedPayload` field
3636
1. Compute Sha256 over the above payload
37-
1. Compute the ECDSA signature of that sha, and place it in the `signatureHash` field
37+
1. Compute the ECDSA signature of that sha, and place it in the `signatureHash`
38+
field, the signature MUST be raw concatenation of r and s.
3839
1. To identify the sender, place a truncated sha of the sender's certificate in `senderCertHash`
3940
1. Place the algorithm used for the truncated sha in the `algo` field. Currently it's either a SHA256-32bytes or SHA256-16bytes. Note that `senderCertHash` is just for a lookup at the receiver, hence it can be truncated to be a lot shorter without any security implications.
4041
1. For the case when the receiver might not be able to identify the sender using just the hash, place the full sender's certificate in the `senderCert` field. This is the base64 standard encoding of the PEM format of the certificate. (This is used for the `register` API during onboarding.)

0 commit comments

Comments
 (0)