-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Dynamic salt length for PKCS#1 v2.1 signing and verification #8
Labels
Comments
Added support for custom labels in PolarSSL 1.2.6 |
gilles-peskine-arm
added a commit
to gilles-peskine-arm/mbedtls
that referenced
this issue
Sep 5, 2017
Msp430 build and test scripts
Patater
added a commit
to Patater/mbedtls
that referenced
this issue
Jan 15, 2019
modify check-names.sh and list-macros.sh to work with PSA constants
hanno-becker
pushed a commit
to hanno-becker/mbedtls
that referenced
this issue
Mar 25, 2020
Enhance documentation of cTLS and TLS 1.3 compatibility mode configuration options
loafer-mka
pushed a commit
to loafer-mka/mbedtls
that referenced
this issue
Jun 22, 2021
bensze01
pushed a commit
to bensze01/mbedtls
that referenced
this issue
Jul 3, 2024
Publish PSA framework simulator
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for adding PKCS #1 v2.1 to the library. I see that the salt length is effectively tied to the hash length with slen=hlen. Can you make the salt length a parameter when calling the sign and verify functions?
Verify automatically uses the salt that is in the signature itself.
For sign, a change is needed. I don't like adding a salt-len variable that is only used if the RSASSA-PSS is enable in the code.. I'm still looking for a nice and not so ugly solution to propagate the salt-len into that part of the code.
Suggestions are welcome.
Postponed to a next release.
The text was updated successfully, but these errors were encountered: