From: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: pgAdmin with SSHTunneling support |
Date: | 2012-11-02 13:16:04 |
Message-ID: | CANxoLDfJaisy0QJyFkqPFA8QAYqb=ZC32rsmKdoE7BYygMXqrw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, Nov 1, 2012 at 5:11 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Thu, Nov 1, 2012 at 11:38 AM, Akshay Joshi
> <akshay(dot)joshi(at)enterprisedb(dot)com> wrote:
> >
> >
> > On Wed, Oct 31, 2012 at 10:30 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> >>
> >> Hi
> >>
> >> On Tue, Oct 23, 2012 at 12:33 PM, Akshay Joshi
> >> <akshay(dot)joshi(at)enterprisedb(dot)com> wrote:
> >> >
> >> > Here the problem is we don't have an entry in the "pgpass" file for
> >> > the
> >> > localip:port pair(one end of the SSH tunnel). At the first attempt to
> >> > connect
> >> > to server it looks for the pgpass entry If stored password is
> >> > checked, in
> >> > this case user will find the error message. In the second attempt it
> >> > first
> >> > prompted for the database password which will be store in the
> >> > variable
> >> > and in this case user will not bet any error and then for the
> subsequent
> >> > attempts it uses the password which is stored in the variable. If
> we
> >> > restart pgAdmin, again the same problem will occur.
> >>
> >> OK, I'm still seeing the issue here. When I first try to connect it
> >> always seems to fail to prompt me for a password and then gives an
> >> error. I think the solution is to simply always ask for the password,
> >> if the server requests it.
> >
> >
> > As I understand you correctly, we will always prompt for the database
> > password and SSH Tunneling password/pass-phrase if SSH tunneling is on
> and
> > even if
> > store password is set to true??
>
> That's what I'm thinking - unless you have another solution that would
> fix the issue and allow the password to be stored (I know we did talk
> about adding temp entries to the file a while back)?
>
> If we're going to ignore saved passwords though, we probably need to
> warn the user when they enable tunnelling (a message box if the option
> is checked perhaps, and then un-check it).
>
Fixed. Attached is the new patch.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
--
*Akshay Joshi
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
Phone: +91 20-3058-9522
Mobile: +91 976-788-8246*
Attachment | Content-Type | Size |
---|---|---|
SSHTunnel_pgAdmin_v2.patch | application/octet-stream | 1.6 MB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2012-11-02 16:33:20 | Re: pgAdmin with SSHTunneling support |
Previous Message | Dave Page | 2012-11-02 12:44:21 | Re: Fix for crash after renaming columns. |