Re: tlsv1 alert iso-8859-1 ca error on cert authentication - Mailing list pgsql-bugs

From Andrus
Subject Re: tlsv1 alert iso-8859-1 ca error on cert authentication
Date
Msg-id 5b918a1a-5105-49dd-94ba-cea1e2018623@hot.ee
Whole thread Raw
In response to Re: tlsv1 alert iso-8859-1 ca error on cert authentication  (Jacob Champion <jacob.champion@enterprisedb.com>)
List pgsql-bugs

Hi!

I wonder if this setup is somewhat undefined/underdefined behavior.

Andrus, if I understand correctly, you have
- two certificates (one client, one server _and_ CA)
- with the same(!) Subject, according to the logs
- one signed the other (so it's "self-signed")
- one is marked CA, one is not

I have no idea how OpenSSL or the RFCs resolve this situation. Do you
really intend to have the CA share the same Subject as the client?

No. It was mistake. You can close this bug report as invalid.

Andrus.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
Next
From: Lowell Hought
Date:
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17