Re: Broken link in pgcrypto documentation

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hanefi(dot)onaldi(at)microsoft(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Broken link in pgcrypto documentation
Date: 2024-02-13 20:55:41
Message-ID: 41B6EE9E-8834-42F5-A7D0-93EF196FC0A9@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

> On 13 Feb 2024, at 21:24, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> On Tue, Feb 13, 2024 at 9:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>>> On 13 Feb 2024, at 20:42, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> I'm a little dubious about the "Technical References" list right below
>>>> it, too. The RFC references are probably useful and stable, and maybe
>>>> the wikipedia ref is OK, but I have little faith in either the
>>>> stability or the long-term relevance of the other two links.
>>
>>> Not even those are all that stable, while the RFCs' in question haven't been
>>> replaced they have all been updated with new RFC's which we don't link to. I
>>> think we are better off removing them as well and leaving reading up on
>>> security/crypto subject an exercise for the reader.
>>
>> Good point. Nuking both lists works for me.
>
> +1.

Alright, sounds good. I'll go ahead with that in the morning then, backpatched
all the way down since the links are equally outdated everywhere.

--
Daniel Gustafsson

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2024-02-15 09:44:42 Stats and the query results on examples seem wrong
Previous Message Magnus Hagander 2024-02-13 20:24:44 Re: Broken link in pgcrypto documentation