Replies: 2 comments 1 reply
-
Hey 👋 It's actually not super simple to add such a config option because the SEIP packet imports (only) the packets it can contain, and the packet parser by itself doesn't actually know about (other) packets anymore. This was done to allow tree shaking, e.g. if you only import functions related to signatures, then you won't need the AES code, etc. So really what we'd need is a config option to pass additional allowed packet classes (which you'd then first need to import yourself), e.g. |
Beta Was this translation helpful? Give feedback.
-
@twiss Thanks for pointing in this direction of the additionalAllowedPackets config option! I created pull request #1618 that implements the concept. |
Beta Was this translation helpful? Give feedback.
-
Hey, I'm running into an issue while upgrading from v4 to v5 and that is due to the restriction of only allowing certain packets inside a SEIP packet. We are using a SEIP packet for a private key backup and so besides a LiteralDataPacket the SEIP also includes all packets that form a private key (SecretKeyPacket,...). I didn't find a way to somehow circumvent the allowedPackets check and wonder if the only way would be to add another config parameter.
Currently there is:
Would it be reasonable to have something like
disableAllowedPacketsCheck: false
?Beta Was this translation helpful? Give feedback.
All reactions