Re: F35 Change: Remove SHA-1 from Sqlite (Self-Contained Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Ben Cotton:

> == 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.

Why can we keep SHA-1 in coreutils and Git, but not in SQLite?  That
does not make sense to me.

SQLite is a general-purpose tool.  Not every use of SHA-1 is
cryptographically relevant.  Most uses in the context of SQLite probably
aren't, so the removal just annoys users for no good reason.

Thanks,
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux