It has been some time since https://bugzilla.mozilla.org/show_bug.cgi?id=1083118 and http://mozilla.6506.n7.nabble.com/Intent-to-unimplement-proprietary-window-crypto-functions-properties-td318535.html and https://pagure.io/dogtagpki/issue/1074
Is implementing this functionality now possible with ff 57+ or it is still the old situation? Shall we ask upstream FF what is their view on supporting similar functionality now they removed support for arbitrary code add-ons?
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
Per PKI Team Meeting of 20180109: 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 0.0 NEEDS_TRIAGE)
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/3003
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)
Login to comment on this ticket.