Re: BUG #17522: While using --with-ssl=openssl and PG_TEST_EXTRA='ssl' options, SSL test fails on OpenBSD 7.1 - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17522: While using --with-ssl=openssl and PG_TEST_EXTRA='ssl' options, SSL test fails on OpenBSD 7.1
Date
Msg-id YrQBYI2YOQmqm/tY@paquier.xyz
Whole thread Raw
In response to Re: BUG #17522: While using --with-ssl=openssl and PG_TEST_EXTRA='ssl' options, SSL test fails on OpenBSD 7.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Wed, Jun 22, 2022 at 12:31:45PM -0400, Tom Lane wrote:
> Jacob Champion <jchampion@timescale.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

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects...
Next
From: Raman Kumar
Date:
Subject: Re: BUG #17524: Increase in WAL size due to logical replication with publication contain a table with low activity.