public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jacobo Sánchez López <[email protected]>
To: [email protected]
Subject: Re: ssh tunneling
Date: Wed, 24 Jan 2024 09:39:37 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <SA1PR17MB53505C81C0DD3D297B7247BFBE742@SA1PR17MB5350.namprd17.prod.outlook.com>
References: <CABbEOvy27FC4ECcGQcPY6u7LCHWqjJT98_2=bfWVCVqCOdYkgA@mail.gmail.com>
<CADK3HHKTNcd5xaTogEPkt0JVSfxNrfg9_UCSVuz0tw+5HvVQXg@mail.gmail.com>
<CADK3HH+oW+6b4U4gEfVmp_7ts5XMjN0ZQN7e=tH8psxgmwj4Kw@mail.gmail.com>
<SA1PR17MB53505C81C0DD3D297B7247BFBE742@SA1PR17MB5350.namprd17.prod.outlook.com>
Maybe the original message is about SSH proxy instead of tunneling?
The PostgreSQL protocol makes a SSH upgrade instead of starting the
communication with SSH handshake and that is a problem when using some
SSH proxies/load balancers which are nowadays common in cloud
environments. I also wish there was a way to connect directly to a SSH
socket but that is not about the driver but how PostgreSQL communication
protocol I guess.
Regards
Jacobo
On 1/23/2024 10:49 PM, Jon Raiford wrote:
>
> As Dave mentions, SSH tunneling should work ok. You need to make sure
> you set up the tunnel correctly. I would suggest testing this using
> something like netcat to make sure the tunnel is working. If you can
> connect to netcat with telnet and PostgreSQL is still not connecting
> then you may want to have a look at your pg_hba.conf configuration to
> make sure it is set up to accept connections from your SSH server.
>
> Jon
>
> *From: *Dave Cramer <[email protected]>
> *Date: *Tuesday, January 23, 2024 at 4:35 PM
> *To: *Juan Ignacio Fernigrini <[email protected]>
> *Cc: *[email protected] <[email protected]>
> *Subject: *Re: ssh tunneling
>
> On Tue, 23 Jan 2024 at 16:06, Dave Cramer <[email protected]>
> wrote:
>
> On Tue, 23 Jan 2024 at 15:28, Juan Ignacio Fernigrini
> <[email protected]> wrote:
>
> Good morning team,
>
> I hope this message finds you well.
>
> I am tasked with establishing a connection to my database
> using ODBC with SSH tunneling. Unfortunately, the current ODBC
> solution is not compatible. I have explored alternatives such
> as Devart, but it comes at a cost of $250. I am considering
> whether it would be more beneficial to invest this amount in
> developing the required feature within the existing
> open-source ODBC solution.
>
> Best regards,
> Juan Ignacio Fernigrini
>
> I'm not sure why psql odbc would not be able to use ssh tunneling.
> Can you expand upon that ?
>
> Dave Cramer
>
> www.postgres.rocks <http://www.postgres.rocks;
>
> see What is an SSH Tunnel & SSH Tunneling?
> <https://www.ssh.com/academy/ssh/tunneling#:~:text=SSH%20tunneling%20is%20a%20method%20of%20transport...;
>
>
> For details it is not part of the driver.
>
> Dave
>
view thread (8+ 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]
Subject: Re: ssh tunneling
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