From: Tomas Pospisek <tpo2@sourcepole.ch>
To: pgsql-general@lists.postgresql.org
Subject: Re: Regarding SSL Enablement in PostgreSQL Database on different port
Date: Tue, 2 May 2023 21:15:08 +0200
Message-ID: <fc7edc62-79f8-74c5-cfb8-08ddca84d32b@sourcepole.ch> (raw)
In-Reply-To: <CABUevEwx7=cCE=SBW7kXamNbVN9Hk4+oMbS2cF0PSSM31HKdvA@mail.gmail.com>
References: <CAAUgb-s9UZXvFsd4Jak78gWv01oKBhnUjC8VvDNxS=Q+Yaq=Ww@mail.gmail.com>
<CABUevEwx7=cCE=SBW7kXamNbVN9Hk4+oMbS2cF0PSSM31HKdvA@mail.gmail.com>
On 02.05.23 12:13, Magnus Hagander wrote:
> On Tue, May 2, 2023 at 11:43 AM sujay kadam <sujaykadam02@gmail.com> wrote:
>>
>> Hi PostgreSQL Team,
>>
>>
>> I want to enable SSL in PostgreSQL Database on a new port.
>>
>> I don’t want the default port that is 5432 SSL enabled, but I want to configure another port to enable SSL on it.
>>
>> As per my requirement, I cannot use the same port for normal connection and SSL connection.
>>
>> Hence, we require a new port to be SSL enabled.
>>
>>
>> Please guide us with proper information and links to achieve the above task.
>
> That is now how SSL in PostgreSQL works. It will always run on the
> same port, and PostgreSQL will only listen on one port.
>
> You can probably do some hacky solution to it by running something
> like pgbouncer on a different port and enable SSL only in that one.
> But it will be a hack. I would recommend instead reviewing your
> requirements and see if you can make them work with how PostgreSQL is
> designed.
Oh, I think your idea to use pgbouncer to take care of the SSL
termination is elegant. I don't think me I'd characterize it as a hack
if properly set up. Why do you consider it a hack?
*t
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tpo2@sourcepole.ch
Subject: Re: Regarding SSL Enablement in PostgreSQL Database on different port
In-Reply-To: <fc7edc62-79f8-74c5-cfb8-08ddca84d32b@sourcepole.ch>
References: <CAAUgb-s9UZXvFsd4Jak78gWv01oKBhnUjC8VvDNxS=Q+Yaq=Ww@mail.gmail.com> <CABUevEwx7=cCE=SBW7kXamNbVN9Hk4+oMbS2cF0PSSM31HKdvA@mail.gmail.com> <fc7edc62-79f8-74c5-cfb8-08ddca84d32b@sourcepole.ch>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox