Bug 1479271 - OpenSSH Server Crypto Policy
Summary: OpenSSH Server Crypto Policy
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 27
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jakub Jelen
QA Contact:
Whiteboard: ChangeAcceptedF27, SelfContainedChange
Depends On: 1477613
Blocks: 1225752
TreeView+ depends on / blocked
Reported: 2017-08-08 08:42 UTC by Jan Kurik
Modified: 2017-12-18 11:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-11-14 08:57:31 UTC
Type: ---

Attachments (Terms of Use)

Description Jan Kurik 2017-08-08 08:42:19 UTC
This is a tracking bug for Change: OpenSSH Server Crypto Policy
For more details, see: https://fedoraproject.org//wiki/Changes/OpenSSH_Server_Crypto_Policy

OpenSSH clients follow the system-wide crypto policy since Fedora 26.
This F27 change modifies the openssh server configuration to adhere to the system-wide policy.
That will allow openssh server configuration to adapt to the multiple security levels offered system-wide.

Comment 1 Jakub Jelen 2017-08-08 09:53:17 UTC
The change should be already in Rawhide and depends on the following SELinxu bug:


Comment 2 Jan Kurik 2017-08-15 08:11:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 3 Jan Kurik 2017-09-06 13:38:21 UTC
On 2017-Sep-05 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 27 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

Comment 4 Jakub Jelen 2017-09-06 14:39:46 UTC
We are done here for some time. Sorry that I didn't change the status before. Fixed now.

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