From: | Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Should I enforce ssl/local socket use? |
Date: | 2020-06-06 20:22:23 |
Message-ID: | CACxu=vKAKTiCmP=6bnjqsi2qgVsPJ4f2WE5VYgp8ysyiVkicaw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
I'm the author of the pgsodium cryptography library. I have a question
about a best practice I'm thinking of enforcing. Several functions in
pgsodium generate secrets, I want to check the Proc info to enforce that
those functions can only be called using a local domain socket or an ssl
connection. If the connection isn't secure by that definition, secret
generating functions will fail.
If someone really wants to point the gun at their foot, they can connect
with an unsecured proxy. My goal would be to make bypassing the check
annoying.
Any thoughts? Is this an insufferably rude attitude? Are there scenarios
where one can foresee needing to generate secrets not over ssl or a domain
socket?
-Michel
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-06-06 20:52:18 | Re: Should I enforce ssl/local socket use? |
Previous Message | Jonathan Strong | 2020-06-06 18:28:52 | Re: Multitenent architecture |