From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, 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:24:44 |
Message-ID: | CABUevEyTt9CAfUwO3hxc4dn0Ex8bnwDq0qYBGtGxtfUHbAWjBQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2024-02-13 20:55:41 | Re: Broken link in pgcrypto documentation |
Previous Message | Tom Lane | 2024-02-13 20:08:24 | Re: Broken link in pgcrypto documentation |