pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Magnus Hagander <mha@sollentuna.net>
Cc: 'pgsql-patches@postgresql.org' <pgsql-patches@postgresql.org>
Subject: Re: RE: SSL Connections [doc PATCH]
Date: Mon, 1 Jan 2001 21:19:28 -0500 (EST)
Message-ID: <200101020219.VAA05439@candle.pha.pa.us> (raw)
In-Reply-To: <215896B6B5E1CF11BC5600805FFEA82104801345@sirius.edu.sollentuna.se>

If this is a valid point, can someone send me a patch for it?  Thanks.

> It looks Ok, but it has one unnecessary step. There is no need to do the "mv
> privkey.pem cert.pem.pw" if you just use "privkey.pem" in the following
> openssl command (e.g. openssl rsa -in privkey.pem -out cert.pem".
> But there is nothing wrong with it as it is now, as far as I can see.
> 
> 
> //Magnus
> 
> 
> > -----Original Message-----
> > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> > Sent: den 21 december 2000 20:15
> > To: Magnus Hagander
> > Cc: 'Matthew Kirkwood'; 'pgsql-patches@postgresql.org'
> > Subject: Re: [PATCHES] RE: SSL Connections [doc PATCH]
> > 
> > 
> > I have applied an earlier patch to this file for SSL.  Could you check
> > the current tree and see how you like it?
> > 
> > 
> > > Thanks for that one!
> > > 
> > > Here is a patch to update the documentation based on this - 
> > this should make
> > > it less dependant on the version of OpenSSL used.
> > > 
> > > //Magnus
> > > 
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Matthew Kirkwood [mailto:matthew@hairy.beasts.org]
> > > > Sent: den 21 december 2000 16:49
> > > > To: Oliver Elphick
> > > > Cc: pgsql-hackers@postgresql.org
> > > > Subject: Re: [HACKERS] SSL Connections
> > > > 
> > > > 
> > > > On Wed, 20 Dec 2000, Oliver Elphick wrote:
> > > > 
> > > > > To create a quick self-signed certificate, use the CA.pl script
> > > > > included in OpenSSL:
> > > > > 
> > > > > CA.pl -newcert
> > > > 
> > > > Or you can do it manually:
> > > > 
> > > > openssl req -new -text -out cert.req (you will have to enter 
> > > > a password)
> > > > mv privkey.pem cert.pem.pw
> > > > openssl rsa -in cert.pem.pw -out cert.pem  (this removes 
> > the password)
> > > > openssl req -x509 -in cert.req -text -key cert.pem -out cert.cert
> > > > 
> > > > Matthew.
> > > > 
> > > 
> > 
> > [ Attachment, skipping... ]
> > 
> > 
> > -- 
> >   Bruce Momjian                        |  http://candle.pha.pa.us
> >   pgman@candle.pha.pa.us               |  (610) 853-3000
> >   +  If your life is a hard drive,     |  830 Blythe Avenue
> >   +  Christ can be your backup.        |  Drexel Hill, 
> > Pennsylvania 19026
> > 
> 


-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (9+ messages)  latest in thread

Message-ID: <200101020219.VAA05439@candle.pha.pa.us>
Permalink:  ../200101020219.VAA05439@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200101020219.VAA05439@candle.pha.pa.us

 · 

reply

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 using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: pgman@candle.pha.pa.us, mha@sollentuna.net, pgsql-patches@postgresql.org
  Subject: Re: RE: SSL Connections [doc PATCH]
  In-Reply-To: <200101020219.VAA05439@candle.pha.pa.us>

* 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