| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jacob Champion <jchampion(at)timescale(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, byavuz81(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17522: While using --with-ssl=openssl and PG_TEST_EXTRA='ssl' options, SSL test fails on OpenBSD 7.1 |
| Date: | 2022-06-24 11:11:23 |
| Message-ID: | 3224e5c6-5385-c33c-b024-f002fdeec21e@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 23.06.22 08:00, Michael Paquier wrote:
> On Wed, Jun 22, 2022 at 12:31:45PM -0400, Tom Lane wrote:
>> Jacob Champion <jchampion(at)timescale(dot)com> writes:
>>> Moving from lax to strict validation means plenty
>>> of IETF spec reading to make sure we don't throw away useful hostnames
>>> by accident.
>>
>> True. I'd be content to disallow '/' and move on.
>
> It does not seem like this is strictly forbidden, either. This set of
> rules would be RFC 1035, section 2.3, I guess:
> https://datatracker.ietf.org/doc/html/rfc1035
>
>> Or we could just drop this test case.
>
> I'd be fine with that. Disabling the SNI, as proposed upthread, would
> also be fine.
I have proceeded with removing the test.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-06-24 12:00:32 | BUG #17531: Push Notification Many Times Show. |
| Previous Message | Julien Rouhaud | 2022-06-24 08:40:26 | Re: dropdb utility command prompts for password despite valid .pgpass file in home directory |