| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | 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>, peter(dot)eisentraut(at)enterprisedb(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-23 06:00:00 |
| Message-ID: | YrQBYI2YOQmqm/tY@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raman Kumar | 2022-06-23 06:33:09 | Re: BUG #17524: Increase in WAL size due to logical replication with publication contain a table with low activity. |
| Previous Message | Tom Lane | 2022-06-23 04:29:18 | Re: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects... |