-
Notifications
You must be signed in to change notification settings - Fork 384
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
RSASSA-PSS #3
RSASSA-PSS #3
Conversation
…n ascending order
This reverts commit 2eb5651.
Conflicts: dss-common/pom.xml dss-demo-applet/src/main/java/eu/europa/ec/markt/dss/applet/util/SigningUtils.java dss-document/src/test/java/eu/europa/ec/markt/dss/validation/InfiniteLoopDSS621Test.java
Any news concerning this pull request? |
Hello Bob, Thanks for your contribution. We added this support for a german TLSO and we are waiting his feedback. We will keep you informed soon. Kind regards, |
Hello Pierrick, |
Hello Pierrick, Have you any idea when you will be able to integrate this pool request? |
Can you please introduce this request as a feature request in JIRA. The new algorithm have to be supported in any environment, can you please add test material ? |
Rotation support for visual signature - Pull request #71
…nknown Fix typo unkown in error message
Hello,
For RSASSA-PSS without Parameters
Identifiers:
http://www.w3.org/2007/05/xmldsig-more#sha3-224-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha3-256-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha3-384-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha3-512-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#md2-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#md5-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha1-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha224-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha256-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha384-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha512-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#ripemd128-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#ripemd160-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#whirlpool-rsa-MGF1
from BC:
algorithms.put("SHA1WITHRSAANDMGF1", PKCSObjectIdentifiers.id_RSASSA_PSS);
algorithms.put("SHA224WITHRSAANDMGF1", PKCSObjectIdentifiers.id_RSASSA_PSS);
algorithms.put("SHA256WITHRSAANDMGF1", PKCSObjectIdentifiers.id_RSASSA_PSS);
algorithms.put("SHA384WITHRSAANDMGF1", PKCSObjectIdentifiers.id_RSASSA_PSS);
algorithms.put("SHA512WITHRSAANDMGF1", PKCSObjectIdentifiers.id_RSASSA_PSS);
You can add more identifiers to the framework but I'm interested in:
http://www.w3.org/2007/05/xmldsig-more#sha1-rsa-MGF1
http://www.w3.org/2007/05/xmldsig-more#sha256-rsa-MGF1
There is no common approach between XML & CMS, the same OID is used for different signature algorithms... It can create some issues.
Thanks,
Bob