Hello,
When I load a .pfx to use for signing output files, like docx or others, if pfx file private key is ML-DSA or ML-KEM or other post quantum certificates, Aspose can’t read it and saves the output file unsigned!
First, post quantum is the future of security, second, seems Aspose Words is already using Bounty Castle, if so, that will be easy, just please properly cast all certificate types.
Best.
@australian.dev.nerds Could you please attach the sample problematic pfx files here for testing? We will check the issue and provide you more information.
1 Like
Hello,
Here it is.
The first official ML-DSA-signed PDFs were successfully generated and exchanged between major PDF architectural leads. For xps oxps doc docx it can be done via internal signer
ML-DSA.zip (58.4 KB)
@australian.dev.nerds
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): WORDSNET-29357
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.