Re: 2nd cut at SSL documentation

From: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
To: Bear Giles <bgiles(at)coyotesong(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 2nd cut at SSL documentation
Date: 2002-05-23 01:50:41
Message-ID: Pine.LNX.4.21.0205230246490.2761-100000@ponder.fairway2k.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers


> On Tue, 21 May 2002 14:27:00 -0600 (MDT)
> "Bear Giles" <bgiles(at)coyotesong(dot)com> wrote:
> > A second cut at SSL documentation....

> [snip]

> > To set up a SSH/OpenSSH tunnel, a shell account for each
> > user should be set up on the database server. It is acceptable
> > for the shell program to be bogus (e.g., /bin/false), if the
> > tunnel is set up in to avoid launching a remote shell.
> >
> > On each client system the $HOME/.ssh/config file should contain
> > an additional line similiar to
> >
> > LocalForward 5555 psql.example.com:5432

I'm coming to this party a bit late in that this is the first I've read the
documentation. I'm also a bit of a newbie when it comes to SSH and I've not
investigated ssh3 at all yet. However, isn't this assuming ssh1 only? I know
ssh2 will fallback to ssh1 compatibility but should there be something about
configuring for the later versions?

--
Nigel J. Andrews
Director

---
Logictree Systems Limited
Computer Consultants

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message terry 2002-05-23 14:49:07 DISTINCT and ORDER BY issue
Previous Message Neil Conway 2002-05-21 23:50:38 Re: [HACKERS] 2nd cut at SSL documentation

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2002-05-23 01:51:07 Re: Redhat 7.3 time manipulation bug
Previous Message Nigel J. Andrews 2002-05-23 01:39:01 Re: Graphical Tool