You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When investigating how we are effected by IntersectMBO/cardano-ledger#2729, I was surprised to find that we handled everything properly. This is because we're not checking any lengths and copying into unbounded byte slices.
We need to make sure that we're doing some sanity checks around sizes/lengths AND that we can also handle the case described in the other issue. This will probably mean silently storing the extra bytes from the address, but they will only be used when generating the bech32 representation of the address.
The text was updated successfully, but these errors were encountered:
When investigating how we are effected by IntersectMBO/cardano-ledger#2729, I was surprised to find that we handled everything properly. This is because we're not checking any lengths and copying into unbounded byte slices.
We need to make sure that we're doing some sanity checks around sizes/lengths AND that we can also handle the case described in the other issue. This will probably mean silently storing the extra bytes from the address, but they will only be used when generating the bech32 representation of the address.
The text was updated successfully, but these errors were encountered: