1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
Hi. It's the signature created by CreateOTAUpdate
through a call to StartSigningJob
. CreateOTAUpdate
creates the signing job with the destination being the same bucket as the source file, and putting the object in the SignedImage
prefix or folder. CreateOTAUpdate
puts two object versions in the same object key: the newer version is the original raw binary file, the older object version is the signed object. This is a JSON file containing the binary in base64 as a payload, and containing the signature. Like this:
{"rawPayloadSize":366816,"signature":"MEUCIDyuNCD5LlP1crNWd/tuqGhLR00YLeXMked9fSDMYYDrAiEAoUM/Z7h4Hr9VmaTxgCJoF+cRA1KZuSXQ3UIRdOQbuFo=","signatureAlgorithm":"SHA256withECDSA","payload":"U0ZVTQEAAQDgkAUAAAAAAOCQBQBye44U047pAAzyQXKlLOlTw3f3TuXyfhtOBdFufo33iHJ7jhTTjukADPJBcqUs6VPDd/dO5fJ+G04F0W5+jfeIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwggJRMIIB ........."}
The signature
key holds the value you need for the job document.
Note that the key in the job document should only be sig-sha256-ecdsa
if the signing algorithm is SHA256withECDSA.
Contenus pertinents
- demandé il y a 4 mois
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans