According to https://tools.ietf.org/html/draft-gutmann-scep-06#section-2.8, AES is now mandatory to implement for SCEP.
AES
Looking at the dogtag code, this should be relatively simple since the underlying logic at https://github.com/dogtagpki/pki/blob/master/base/server/cms/src/com/netscape/cms/servlet/cert/scep/CRSEnrollment.java#L1125-L1130 seems to just choose between DES and DES3 without allowing for other ciphers.
DES
DES3
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @mharmsen: - Issue priority set to: critical - Issue set to the milestone: 10.6 (was: 0.0 NEEDS_TRIAGE)
Hi, thank you for bringing up the issue. Would you be interested in contributing to the code by providing a patch? From time to time we get patch contributions from the community and we find such practice beneficial to all parties due to limited resources on our end. The process will require the contributor to provide a working patch against the master, complete with details on how it's setup and the testing procedure. The Dogtag team will then assign someone to review the code. Once the fix is hashed out, patch will be checked in with proper credit given to the contributor.
Please let us know.
@cfu I don't mind in theory but I have no idea when I'll be able to get to it since I'm currently trying to patch both certmonger and sscep to work properly.
certmonger
sscep
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/3035
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)