On Wed, 2021-07-14 at 14:13 -0400, Paul Wouters wrote:
> On Mon, 12 Jul 2021, Simo Sorce wrote:
>
> > > 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
This change won't be applied, so no action is required.
Ondrej
On Wed, Jul 14, 2021 at 8:14 PM Paul Wouters wrote:
> On Mon, 12 Jul 2021, Simo Sorce wrote:
>
> >> SQLite is a general-purpose tool. Not every use of SHA-1 is
> >> cryptographically relevant. Most uses in the context of SQLite
On Mon, 12 Jul 2021, Simo Sorce wrote:
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.
Note that this is a Sqlite decision, from RHEL engineering
On Fri, 2021-07-09 at 20:22 +0200, Florian Weimer wrote:
> * 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
Hello,
According to the response from upstream [1], it seems I have come up with a
solution too quickly. I apologize for this. I will go through a
cancellation process of this Change Proposal, as there seems to be no valid
reason to remove SHA-1 support in sqlite.
Thanks for your help and
On Sat, Jul 10, 2021 at 12:13:20AM +0200, Felix Schwarz wrote:
>
> Am 09.07.21 um 17:45 schrieb 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
Am 09.07.21 um 17:45 schrieb 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.
I don't think that
* 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
On 7/9/21 11:48 AM, Ben Cotton wrote:
On Fri, Jul 9, 2021 at 11:45 AM Ben Cotton wrote:
== Upgrade/compatibility impact ==
SHA-1 algorithm will not be supported in sqlite. Instead SHA-3
algorithm can be used.
== User Experience ==
Users won't be able to use SHA-1 algorithm with sqlite.
On 7/9/21 11:45 AM, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/Sqlite_SHA-1
== Summary ==
Removal of deprecated crypto algorithm SHA-1 from sqlite.
== Owner ==
* Name: [[User:odubaj| Ondrej Dubaj]]
* Email: odu...@redhat.com
== Detailed Description ==
The use of SHA-1 is no
On Fri, Jul 9, 2021 at 11:45 AM Ben Cotton wrote:
>
> == Upgrade/compatibility impact ==
> SHA-1 algorithm will not be supported in sqlite. Instead SHA-3
> algorithm can be used.
>
> == User Experience ==
> Users won't be able to use SHA-1 algorithm with sqlite. Instead, they
> can use SHA-3
https://fedoraproject.org/wiki/Changes/Sqlite_SHA-1
== Summary ==
Removal of deprecated crypto algorithm SHA-1 from sqlite.
== Owner ==
* Name: [[User:odubaj| Ondrej Dubaj]]
* Email: odu...@redhat.com
== Detailed Description ==
The use of SHA-1 is no longer permitted for Digital Signatures or
https://fedoraproject.org/wiki/Changes/Sqlite_SHA-1
== Summary ==
Removal of deprecated crypto algorithm SHA-1 from sqlite.
== Owner ==
* Name: [[User:odubaj| Ondrej Dubaj]]
* Email: odu...@redhat.com
== Detailed Description ==
The use of SHA-1 is no longer permitted for Digital Signatures or
13 matches
Mail list logo
