Hello,
Similarly to #955 for CMSSignedData class, a method #addDigestAlgorithm(s) should be added within CMSSignedDataParser, allowing to generate a new CMS, with a custom set of digest algorithms.
The current code has limitations on storing digest algorithms used within counter-signatures, as well as for archive-time-stamp-v3 (see ETSI EN 319 122-1, "5.5.3 The archive-time-stamp-v3 attribute").
This currently limits our implementation from upgrading from CMSSignedData to CMSSignedDataParser, thus allowing signing and augmentation of large CMSs (CMS signing huge documents, i.e. 2GB+).
Thank you in advance.
Best regards,
Aleksandr
Hello,
Similarly to #955 for CMSSignedData class, a method #addDigestAlgorithm(s) should be added within CMSSignedDataParser, allowing to generate a new CMS, with a custom set of digest algorithms.
The current code has limitations on storing digest algorithms used within counter-signatures, as well as for archive-time-stamp-v3 (see ETSI EN 319 122-1, "5.5.3 The archive-time-stamp-v3 attribute").
This currently limits our implementation from upgrading from CMSSignedData to CMSSignedDataParser, thus allowing signing and augmentation of large CMSs (CMS signing huge documents, i.e. 2GB+).
Thank you in advance.
Best regards,
Aleksandr