Skip site navigation (1) Skip section navigation (2)

Re: SSH Tunneling implementation

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: SSH Tunneling implementation
Date: 2012-07-08 19:46:27
Message-ID: (view raw or whole thread)
Lists: pgadmin-hackers
On Fri, Jul 6, 2012 at 6:17 PM, Ashesh Vashi

>> Shouldn't be needed, no. The client presents the private key, the
>> server will automatically find the corresponding public key (or
>> complain that it can't).
> Exactly.
> It should be Identity file (private key - not public key)
> One thing, missing is the passphrase of the identity file.
> I had conversation with Akshay regarding it.
> We were agree to change the label for password to Password/Pass Phrase and
> the certificate to 'Identity File'.
> So - the same textbox can be used to take password. And, pass-phrase in
> case of identity file is provided.
> And - add a label to show tip about the Password/Pass-phrase at the bottom
> of the dialog to explain that use of the text-box.
That may not be necessary - but I guess the fields should be re-ordered so
the password/passphrase box is at the bottom. It would be more of a logical
flow that way.

Dave Page
Twitter: @pgsnake

EnterpriseDB UK:
The Enterprise PostgreSQL Company

In response to

pgadmin-hackers by date

Next:From: Akshay JoshiDate: 2012-07-09 09:10:18
Subject: Re: SSH Tunneling implementation
Previous:From: Ashesh VashiDate: 2012-07-06 17:17:02
Subject: Re: SSH Tunneling implementation

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group