Bug 1340846 - NSS enforces the system-wide crypto policy
Summary: NSS enforces the system-wide crypto policy
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 25
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Nikos Mavrogiannopoulos
QA Contact:
Whiteboard: ChangeAcceptedF25, SelfContainedChange
Depends On: 1157720
TreeView+ depends on / blocked
Reported: 2016-05-30 12:05 UTC by Jan Kurik
Modified: 2016-11-22 13:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-11-22 13:58:45 UTC
Type: ---

Attachments (Terms of Use)

Description Jan Kurik 2016-05-30 12:05:09 UTC
This is a tracking bug for Change: NSS enforces the system-wide crypto policy
For more details, see: https://fedoraproject.org//wiki/Changes/NSSCryptoPolicies

As it is now, the System-wide crypto policy in F24 is only enforced by the OpenSSL and GnuTLS TLS libraries. To harmonize crypto in Fedora, NSS is enhanced to respect the settings of the system-wide crypto policy as well.

Comment 1 Jan Kurik 2016-07-26 04:50:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 2 Jan Kurik 2016-07-26 05:22:30 UTC
On 2016-July-26, we have reached Fedora 25 Change Checkpoint: Completion deadline (testable).

At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well.

Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.

Incomplete and non testable Changes will be reported to FESCo on 2016-July-29 meeting.

Comment 3 Jan Kurik 2016-09-29 09:06:06 UTC
On 2016-Sep-27 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 25 release. At this point all the Changes not at least in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review.

Thanks, Jan

Note You need to log in before you can comment on or make changes to this bug.