Change: Disable in Kernel Crypto Userspace API (Phase 1) #3667
Labels
No labels
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
Status
Accepted
Status
Duplicate
Status
Insufficient data
Status
Invalid
Status
Rejected
system wide change
updates policy exception
vote-in-progress
No milestone
No project
No assignees
8 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fesco/tickets#3667
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The in kernel Crypto Userspace API (CRYPTO_USER_API) is now deprecated upstream, with some parts of it being actively removed early in the 7.2 cycle, because of the security risk it contains. It is due to be disabled and actively removed from upstream in the near future. Restrict it's use in Fedora to known active users early so we can do a controlled ending of support and can make the community aware of it's pending disappearance and gracefully deal with unknown users.
Owners, do not implement this work until the FESCo vote has explicitly ended.
When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the FESCo ticket policy and the Changes policy for more information.
If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update.
REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.
Cc @pbrobinson @jforbes
+1
Note: the changes we are putting in here will land in the 7.3 kernel, F-45 will ship GA with the 7.2 kernel, but 7.3 will likely land shortly after GA, this allows testing and advertising of the change so there is awareness. It's likely not nice for users to install F-45 to discover something breaks shortly afterwards.
+1
@pbrobinson wrote in #3667 (comment):
It may be worth preempting this and doing it early in 7.2.
So, to clarify, is change going to trickle down into F44 and F43 too when they get the 7.3 kernel update?
@ngompa wrote in #3667 (comment):
That is the whole point of this proposal.
@decathorpe wrote in #3667 (comment):
@pbrobinson @jforbes, can you please clarify here?
Re. approving this Change for f45: +1
@decathorpe wrote in #3667 (comment):
It will not. we have a mechanism to revert the patches for specific Fedora versions.
+1
Thanks, with this clarification I'm +1 too.
After one week: APPROVED (+5, 0, -0)