| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Damien Clochard <damien(at)dalibo(dot)info> |
| Cc: | pgsql-www(at)lists(dot)postgresql(dot)org |
| Subject: | Re: CVE Links are broken on the PG 10.1 news page |
| Date: | 2017-11-10 13:56:55 |
| Message-ID: | 4665D329-3AB1-41AB-91E9-34B3E4C59A73@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
> On 10 Nov 2017, at 12:14, Damien Clochard <damien(at)dalibo(dot)info> wrote:
>
> Le 10.11.2017 11:17, Daniel Gustafsson a écrit :
>>> On 10 Nov 2017, at 11:15, Damien Clochard <damien(at)dalibo(dot)info> wrote:
>>> here :
>>> https://www.postgresql.org/about/news/1801/
>>> The 3 CVE links lead to a 404 page on RH website :
>>> https://access.redhat.com/security/cve/CVE-2017-12172
>>> https://access.redhat.com/security/cve/CVE-2017-15098
>>> https://access.redhat.com/security/cve/CVE-2017-15099
>> IIRC that’s the case with every security release, the Redhat site aren’t
>> publishing them immediately but will eventually (soonish) have them.
>
> Ok I was not aware of that. It makes sense but maybe we could had this explanation in the release announcement so that people like me don't get confused by the broken links ? :)
Even better would probably be to not make them actual links until the target
URL exists.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-11-10 13:57:57 | Re: CVE Links are broken on the PG 10.1 news page |
| Previous Message | Damien Clochard | 2017-11-10 11:14:29 | Re: CVE Links are broken on the PG 10.1 news page |