| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add SQL function for SHA1 |
| Date: | 2021-01-26 09:38:43 |
| Message-ID: | A13E184C-45A1-4538-A027-E30D575054C2@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 26 Jan 2021, at 04:28, Noah Misch <noah(at)leadboat(dot)com> wrote:
>
> On Mon, Jan 25, 2021 at 10:12:28PM +0900, Michael Paquier wrote:
>> SHA-1 is now an option available for cryptohashes, and like the
>> existing set of functions of SHA-2, I don't really see a reason why we
>> should not have a SQL function for SHA1.
>
> NIST deprecated SHA1 over ten years ago. It's too late to be adding this.
Agreed, and pgcrypto already allows for using sha1.
It seems like any legitimate need for sha1 could be better served by an
extension rather than supplying it in-core.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2021-01-26 09:43:21 | Re: Protect syscache from bloating with negative cache entries |
| Previous Message | Drouvot, Bertrand | 2021-01-26 09:31:33 | Re: [UNVERIFIED SENDER] Re: Minimal logical decoding on standbys |