Thread: feature request - automatic SSH tunnels

I have a feature request for pgAdmin that would help me and other users a lot, 
and I don't see it on your roadmap or TODO.

This is to add to Server Registration extra fields for configuring an SSH tunnel 
so that users can use pgAdmin over an SSH tunnel without having to separately 
setup the tunnel outside pgAdmin.

For example, currently users have to do something like this on the command-line 
when they want to use pgAdmin over a tunnel:
  ssh -L 5423:localhost:5432 postgres@mydomain.com

But ideally pgAdmin would set that up the tunnel automatically when you do a 
Connect.

Even MySQL Workbench has supported this for a few years at least.

How difficult would it be to add this feature, and is there any reason not to?

Would it help if I monetarily sponsored an automatic SSH tunnel feature?

I'm hoping this could make it into 1.18.0 at the latest, if not 1.16.x.

Thank you in advance.

-- Darren Duncan

<p dir="ltr">Darren in whish OS your users are working currently?<br /> And ssh passwords you see them as saved or as
enteredat each conect?<p dir="ltr">Regards, Alexander Yerenkow<div class="gmail_quote">05.04.2013 21:31 пользователь
"DarrenDuncan" <<a href="mailto:darren@darrenduncan.net">darren@darrenduncan.net</a>> написал:<br
type="attribution"/><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">I have a feature request for pgAdmin that would help me and other users a lot, and I don't see
iton your roadmap or TODO.<br /><br /> This is to add to Server Registration extra fields for configuring an SSH tunnel
sothat users can use pgAdmin over an SSH tunnel without having to separately setup the tunnel outside pgAdmin.<br /><br
/>For example, currently users have to do something like this on the command-line when they want to use pgAdmin over a
tunnel:<br/><br />   ssh -L 5423:localhost:5432 <a href="mailto:postgres@mydomain.com"
target="_blank">postgres@mydomain.com</a><br/><br /> But ideally pgAdmin would set that up the tunnel automatically
whenyou do a Connect.<br /><br /> Even MySQL Workbench has supported this for a few years at least.<br /><br /> How
difficultwould it be to add this feature, and is there any reason not to?<br /><br /> Would it help if I monetarily
sponsoredan automatic SSH tunnel feature?<br /><br /> I'm hoping this could make it into 1.18.0 at the latest, if not
1.16.x.<br/><br /> Thank you in advance.<br /><br /> -- Darren Duncan<br /><br /><br /> -- <br /> Sent via
pgadmin-supportmailing list (<a href="mailto:pgadmin-support@postgresql.org"
target="_blank">pgadmin-support@postgresql.<u></u>org</a>)<br/> To make changes to your subscription:<br /><a
href="http://www.postgresql.org/mailpref/pgadmin-support"
target="_blank">http://www.postgresql.org/<u></u>mailpref/pgadmin-support</a><br/></blockquote></div> 

On 2013.04.05 11:40 AM, Alexander Yerenkow wrote:
> Darren in whish OS your users are working currently?
> And ssh passwords you see them as saved or as entered at each conect?
>
> Regards, Alexander Yerenkow

Thanks for your quick response.

We have a mixed-platform environment, but in particular I and several others use
Mac OS X, version 10.6.8 in my case.

Currently I actually do this, having a block like this in my .ssh/config :
    Host foohost        Hostname some.longer.domain        Port 22        User mysshuser        IdentityFile
~/.ssh/id_rsa       ForwardAgent yes        LocalForward 5434 someprivatehost:5432 

And so, before starting up pgAdmin, I have to do this manually on the command line:
    ssh foohost

In pgAdmin, the Server -> Properties cite localhost/5434 as Host/Port then the
usual database name and username.

The absolute minimum that I would like from an enhanced pgAdmin is that I would
not have to do the "ssh foohost" each time I start the program or a connection.

The more ideal thing is that I could just plug the 'some.longer.domain' and '22'
and 'mysshuser' and the identity file or password or whatever into pgAdmin.

In particular, users should not have to specify the local port number of the
tunnel eg 5434, pgAdmin should just be able to pick an available high-numbered
port itself on each run.

Something else that MySQL Workbench does on Mac OS X is utilize the operating
system KeyChain feature so that remembered passwords, if any are encrypted.  But
remembering passwords in a non-plaintext manner would be a separate task for
pgAdmin if it were taken on, and may be more operating-system specific.

Not having to manually run some other setup command prior to each opening of
pgAdmin is the minimal request.

Thank you.

-- Darren Duncan

> 05.04.2013 21:31 пользователь "Darren Duncan" <darren@darrenduncan.net> написал:
>
>     I have a feature request for pgAdmin that would help me and other users a
>     lot, and I don't see it on your roadmap or TODO.
>
>     This is to add to Server Registration extra fields for configuring an SSH
>     tunnel so that users can use pgAdmin over an SSH tunnel without having to
>     separately setup the tunnel outside pgAdmin.
>
>     For example, currently users have to do something like this on the
>     command-line when they want to use pgAdmin over a tunnel:
>
>        ssh -L 5423:localhost:5432 postgres@mydomain.com
>
>     But ideally pgAdmin would set that up the tunnel automatically when you do a
>     Connect.
>
>     Even MySQL Workbench has supported this for a few years at least.
>
>     How difficult would it be to add this feature, and is there any reason not to?
>
>     Would it help if I monetarily sponsored an automatic SSH tunnel feature?
>
>     I'm hoping this could make it into 1.18.0 at the latest, if not 1.16.x.
>
>     Thank you in advance.
>
>     -- Darren Duncan

On Fri, 2013-04-05 at 11:30 -0700, Darren Duncan wrote:
> I have a feature request for pgAdmin that would help me and other users a lot, 
> and I don't see it on your roadmap or TODO.
> 
> This is to add to Server Registration extra fields for configuring an SSH tunnel 
> so that users can use pgAdmin over an SSH tunnel without having to separately 
> setup the tunnel outside pgAdmin.
> 
> For example, currently users have to do something like this on the command-line 
> when they want to use pgAdmin over a tunnel:
> 
>    ssh -L 5423:localhost:5432 postgres@mydomain.com
> 
> But ideally pgAdmin would set that up the tunnel automatically when you do a 
> Connect.
> 
> Even MySQL Workbench has supported this for a few years at least.
> 
> How difficult would it be to add this feature, and is there any reason not to?
> 
> Would it help if I monetarily sponsored an automatic SSH tunnel feature?
> 
> I'm hoping this could make it into 1.18.0 at the latest, if not 1.16.x.
> 

Surely not 1.16 as it's already out, and only bugfixes are done to this
release.

1.18, could be. I remember that one of the EDB's guy was working on
this. Not sure what the status of this patch is though.


-- 
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com

On Fri, 2013-04-05 at 11:30 -0700, Darren Duncan wrote:
> I have a feature request for pgAdmin that would help me and other users a lot,
> and I don't see it on your roadmap or TODO.
>
> This is to add to Server Registration extra fields for configuring an SSH tunnel
> so that users can use pgAdmin over an SSH tunnel without having to separately
> setup the tunnel outside pgAdmin.
>
> For example, currently users have to do something like this on the command-line
> when they want to use pgAdmin over a tunnel:
>
>    ssh -L 5423:localhost:5432 postgres@mydomain.com
>
> But ideally pgAdmin would set that up the tunnel automatically when you do a
> Connect.
>
> Even MySQL Workbench has supported this for a few years at least.
>
> How difficult would it be to add this feature, and is there any reason not to?
>
> Would it help if I monetarily sponsored an automatic SSH tunnel feature?
>
> I'm hoping this could make it into 1.18.0 at the latest, if not 1.16.x.
>

Surely not 1.16 as it's already out, and only bugfixes are done to this
release.

1.18, could be. I remember that one of the EDB's guy was working on
this. Not sure what the status of this patch is though.

On 2013.04.05 4:00 PM, Dave Page wrote:
> The patch is in my inbox. We've been having trouble with it on Mac, though it
> works fine on Linux and Windows (and is actually in the current release version
> of Postgres Enterprise Manager).

Given that my platform is Mac, is there anything I can do to help resolve this? 
-- Darren Duncan

Hi

On Thu, Apr 18, 2013 at 10:16 PM, Darren Duncan <darren@darrenduncan.net> wrote:
> On 2013.04.05 4:00 PM, Dave Page wrote:
>>
>> The patch is in my inbox. We've been having trouble with it on Mac, though
>> it
>> works fine on Linux and Windows (and is actually in the current release
>> version
>> of Postgres Enterprise Manager).
>
>
> Given that my platform is Mac, is there anything I can do to help resolve
> this? -- Darren Duncan

You can help test and debug if you like. We're waiting on an updated
patch from Akshay at the moment (the last one needed some tweaks as
I'd changed part of the build system), but I know he's been a little
busy this week. Hopefully he can post an updated patch in the day or
so.


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company