Lines Matching refs:to
3 When the ECDSA SECP256R1 (EC256) signature support was added to MCUboot, a
4 shortcut was taken, and these signatures were padded to make them
9 There are two ways to fix this:
12 at least one pad byte to always be added (to set the length). This
20 that the length does not need to be known until the signature is
28 This document proposes a multi-stage approach to give a transition
31 1. Add a `--no-pad-sig` argument to the sign command in
39 2. MCUboot will be modified to allow unpadded signatures right away.
42 to accept padded and unpadded signatures.
45 the `--no-pad-sig` signature to be able to boot all generated
50 relevant channels, the arguments to `imgtool.py` will change:
56 This will require an update to any scripts that will rely on the default
60 time the boot code begins to accept unpadded signatures. The simulator is
83 Originally, MCUboot added padding to the entire signature and just
84 removed any trailing 0 bytes from the data block. This turned out to be fine 255 out of 256
89 The correct approach here is to accept that ECDSA signatures are of
90 variable length, and to make sure that we can handle them as such.