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 allocating space for an invoice's bytes, it was assumed that the
bytes used for the invoice request signature are the same length as
those used for the invoice's signature. However, fuzz testing revealed
that this isn't always the case since an invoice request could contain
more than one signature TLV. Account for this when determining the
number of bytes to allocate for the invoice. This comes at the expense
of an additional traversal of all TLVs in the invoice request through
the end of SIGNATURE_TYPES (i.e., every TLV except experimental ones).
0 commit comments