Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
2a1e4a90
Commit
2a1e4a90
authored
22 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Add Bear's SSL comments.
parent
6d0d15c4
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/backend/libpq/README.SSL
+28
-0
28 additions, 0 deletions
src/backend/libpq/README.SSL
with
28 additions
and
0 deletions
src/backend/libpq/README.SSL
+
28
−
0
View file @
2a1e4a90
...
@@ -51,3 +51,31 @@
...
@@ -51,3 +51,31 @@
| Yes
| Yes
|
|
Fail with unknown
Fail with unknown
Comments from Bear Giles:
On a related note, I had mentioned this before but it's a subtle point
and I'm sure that it's slipped everyone's mind...
- if you need to have confidence in the identity of the database
server, e.g., you're storing sensitive information and you absolutely
must prevent any "man in the middle" attacks, use the SSL code I
provided with server-side certs. To many users, the key issue is not
whether the data is encrypted, it's whether the other party can be
trusted to be who they claim to be.
- if you just need confidentiality, but you don't need to verify the
identity of the database server (e.g., because you trust the IP address,
but worry about packet sniffers), SSH tunnels are much easier to set up
and maintain than the embedded SSL code. You can set up the database
server so it doesn't require a certificate (hell, you can hard code a
fallback certificate into the server!), *but that violates the common
practice of SSL-enabled servers.* I cannot overemphasize this - every
other SSL-enabled server requires a certificate, and most provide
installation scripts to create a "snake oil" temporary certificate. I
can't think of any server (apache+mod_ssl, courier-imap, postfix(+tls),
etc.) that uses anonymous servers.
- if you don't need confidentiality, e.g., you're on a trusted network
segment, then use direct access to the server port.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment