From Fedora Project Wiki
m
Line 111: Line 111:
== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
SHA-1 algorithm will not be supported in sqlite. Instead SHA-3 algorithm can be used.


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== How To Test ==
== How To Test ==

Revision as of 08:21, 9 July 2021


Sqlite SHA-1

Summary

Removal of deprecated crypto algorithm SHA-1 from sqlite.

Owner


Current status

  • Targeted release: Fedora 35
  • Last updated: 2021-07-09
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

The use of SHA-1 is no longer permitted for Digital Signatures or authentication in RHEL-9. Due to this reason, there is a need to remove SHA-1 extension from sqlite in RHEL-9 and therefore also Fedora. The removal of the extension was discussed with sqlite upstream development, who confirmed, that it is safe to remove it and should not impact other functionality of sqlite.

Feedback

Benefit to Fedora

This change brings update in terms of removing usage of deprecated crypto algorithms as users should not use them. Also it keeps Fedora project up-to-date with the newest RHEL release, what is beneficial for future releases.

Scope

  • Proposal owners:
    • Prepare patch for removing SHA-1 algorithm from sqlite
    • Discuss the possible issues with upstream
    • Push the changes to Fedora
  • Other developers:
    • Do not use SHA-1 algorithm in sqlite
  • Policies and guidelines: N/A (not needed for this Change)
    • No guidelines need to be updated according to this change
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

SHA-1 algorithm will not be supported in sqlite. Instead SHA-3 algorithm can be used.


How To Test

User Experience

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes