| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rajeshwar Singh <singh(dot)rajeshwar(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SSL enabled connection for PostgreSQL |
| Date: | 2023-06-05 20:43:01 |
| Message-ID: | CAKFQuwa00VY70PbuFBnN-ig2_gWsH_V1W-a+LKp=bKG_Rcy=AA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Monday, June 5, 2023, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
>
>
> On Monday, June 5, 2023, Rajeshwar Singh <singh(dot)rajeshwar(at)gmail(dot)com>
> wrote:
>
>> Hi...
>>
>> I am setting up PostgreSQL 14 with SSL and passphrase. The
>> postgresql.conf file has following entry:
>>
>> ssl=on
>> .
>> .
>> ssl_passphrase_command='passphrase.txt'
>> ssl_passphrase_command_supports_reloads = on
>>
>> Now when I try to connect using psql, it ask for *Enter PEM pass_phrase*:
>>
>> Is there a way where client can be configured so it doesn't ask for pass
>> phrase
>>
>
> Go and re-read how ssl_passphrase_command works and then write a command
> that behaves in a compatible manner?
>
>
Never mind, you are asking about the client…though the server config itself
still seems incorrect.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jorge Silva | 2023-06-07 21:19:01 | Allow an user (not superuser) to create a testing database from a production database |
| Previous Message | David G. Johnston | 2023-06-05 20:40:13 | Re: SSL enabled connection for PostgreSQL |