public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Pavel Golub <[email protected]>
Cc: [email protected]
Subject: Re: Lack of docs for libpq C Library
Date: Thu, 31 Jan 2008 12:14:54 -0500 (EST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Tom Lane wrote:
> Bruce Momjian <[email protected]> writes:
> > Tom Lane wrote:
> >> PQinitSSL *is* documented, though looking at the para immediately raises
> >> the question what the heck we are doing pointing to a random hp.com page
> >> for SSL documentation.
> 
> > I added that for 8.3.  The HP documentation seemed excellent, which is
> > why I added it.
> 
> The question is not about whether that doc is good, bad, or indifferent;
> it is about the likely lifespan of the URL.  A URL containing mostly
> random numbers instead of words does not fill me with confidence.

True, and Magnus was concerned about that as well.  What I liked about
it was the diagrams which I haven't seen anywhere else.  Our doc
reference is:

	(See http://h71000.www7.hp.com/DOC/83final/BA554_90007/ch04s02.html  for
	diagrams showing SSL certificate usage.)

I put it in parentheses to highlight the URL is only for reference to
the diagrams and explaination.  We can either remove the URL or remove
it if the URL changes.

SSL is pretty complicated so when I saw something that made it clearer,
I added it.

> Furthermore HP is hardly the authoritative reference on SSL.  Can't
> we find an RFC or something?

See above.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

view thread (25+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Lack of docs for libpq C Library
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox