-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tolerance to Base64URLSafe encoding padding (or lack thereof) in Connection Protocol Signatures #1053
Comments
gmulhearn
pushed a commit
that referenced
this issue
Dec 19, 2023
* lli - Allow decoding both padded and unpadded Base64 data Signed-off-by: lli <lli@anonyome.com> * lli - Running cargo fmt Signed-off-by: lli <lli@anonyome.com> * lli - improve testing rigor Signed-off-by: lli <lli@anonyome.com> * lli - custom GeneralPurpose engine instance for indifferent decode Signed-off-by: lli <lli@anonyome.com> * lli - move custom engine to utils Signed-off-by: lli <lli@anonyome.com> --------- Signed-off-by: lli <lli@anonyome.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During the Connection Response of Connection Protocol, a signature is attached within a
connection~sig
decorator/field. https://github.com/hyperledger/aries-rfcs/tree/main/features/0160-connection-protocol#2-connection-response .The spec describes it as so, but does not specify whether
base64URL
is with or without padding.There is a note elsewhere on the page which says:
This makes me believe that this sentiment would apply for
sig_data
too. As such, we may want to make our code handle both. Currentlycommon/signing.rs
is hardcoded to useURL_SAFE
(expects padding). It has been found that the animo.demo.id DEMO (which presumably uses AFJ) can producesig_data
which does not have padding. This causes common/signing.rs to throw an InvalidPadding error.payload from animo:
reproducable error:
The text was updated successfully, but these errors were encountered: