age.Decrypt parses headers of arbitrary size into memory, @sweis reported in #699.
Usually, I dislike baking arbitrary limits into lower levels and prefer applications applying the limits that make sense for them at the input. Among other reasons, because it's hard to find one size to fit all applications. However, here there is one thing that is opaque to applications: the header/payload separation.
Opening an issue hoping to find a nicer solution. @str4d, how does rage handle this?
age.Decrypt parses headers of arbitrary size into memory, @sweis reported in #699.
Usually, I dislike baking arbitrary limits into lower levels and prefer applications applying the limits that make sense for them at the input. Among other reasons, because it's hard to find one size to fit all applications. However, here there is one thing that is opaque to applications: the header/payload separation.
Opening an issue hoping to find a nicer solution. @str4d, how does rage handle this?