Bug 1670398

Summary:	krb5 crypto modernization
Product:	[Fedora] Fedora	Reporter:	Ben Cotton <bcotton>
Component:	Changes Tracking	Assignee:	Robbie Harwood <rharwood>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	bcotton, rharwood
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-14 14:18:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ben Cotton 2019-01-29 13:33:12 UTC

This is a tracking bug for Change: krb5 crypto modernization
For more details, see: https://fedoraproject.org/wiki/Changes/krb5_crypto_modernization

krb5 will be removing support for DES, 3DES, crc-32, and MD4 entirely; they will not be allowed in session keys or long-term keys.  Additionally, RC4 and MD5 will be marked deprecated and dangerous.

Comment 1 Ben Cotton 2019-02-19 20:30:24 UTC

According to the Fedora 30 schedule[1], today is the deadline for changes to be in a testable state. If your change is ready to be tested, please set the status to MODIFIED. If you know your change will not be ready for Fedora 30, you can set the version to rawhide and notify bcotton. For more information about this milestone, see the Changes Policy[2].

[1] https://fedoraproject.org/wiki/Releases/30/Schedule
[2] https://fedoraproject.org/wiki/Changes/Policy#Change_Checkpoint:_Completion_deadline

Comment 2 Robbie Harwood 2019-02-19 21:39:55 UTC

It's testable, but the tests will just show it's not done :)  I give it even odds of making the deadline - and if it doesn't, we'll back it off to fc31.

Comment 3 Ben Cotton 2019-03-05 21:50:03 UTC

We have reached the Code Complete (100%) milestone in the Fedora 30 development cycle. At this point, all Changes should be fully code complete and ready for testing during the beta freeze. If your Change has reached this milestone, please set the status to ON_QA. If it has not, this Change will be submitted to FESCo to evaluate the contigency plan and decide if the Change will continue in the Fedora 30 cycle.

Comment 4 Robbie Harwood 2019-03-06 19:05:11 UTC

I'm not done.  Drop it from this release and I'll try for it again in a future one.  Thanks!

Comment 5 Ben Cotton 2019-03-08 16:42:18 UTC

Bumped it to F31. If you think it will be later than that, I'll just pull it entirely and you can resubmit when you're ready.

Comment 6 Ben Cotton 2019-08-13 19:32:13 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 7 Robbie Harwood 2019-08-14 14:18:36 UTC

Complete as it's going to get.