![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
I know that after ssh you can use psql without any problems. What are you using for postgresql - pgadmin.. |
#2
| |||
| |||
|
|
I know that after ssh you can use psql without any problems. What are you using for postgresql - pgadmin.. |
#3
| |||
| |||
|
|
I know that after ssh you can use psql without any problems. What are you using for postgresql - pgadmin.. |
#4
| |||
| |||
|
|
Hi Ron, I've got the puTTY via ssh working well. So, you're saying I can puTTY via ssh to connect to the linux box and postgresql server, and then start pgAdminIII and I'll be able to use the GUI app. with the postgres database. Once you putty into the box (assuming you are user postgres, or whoever |
|
No Cygwin necessary for this situation? No cygwin needed. |
|
Please let me know if I'm understanding this correctly when you have a moment. Thanks for your guidance and input. Mike Ron |
#5
| |||
| |||
|
|
Mike wrote: Hi Ron, I've got the puTTY via ssh working well. So, you're saying I can puTTY via ssh to connect to the linux box and postgresql server, and then start pgAdminIII and I'll be able to use the GUI app. with the postgres database. Once you putty into the box (assuming you are user postgres, or whoever owns the postmaster), you can psql into the database eg psql myDB You don't need to putty into the box to use pgAdmin, you just tell pgAdmin the ip address, user (postgres), and password (unless it's trusted). This works as long as you've allowed access from your remote ip address eg in /data/pg_hba.conf you might have something like this host all all 24.233.244.45 255.255.255.255 trust this line trusts all users connecting from 24.233.244.45, so for example pgAdmin could gain db access. No Cygwin necessary for this situation? No cygwin needed. Please let me know if I'm understanding this correctly when you have a moment. Thanks for your guidance and input. Mike Ron |
#6
| |||
| |||
|
|
I know that after ssh you can use psql without any problems. What are you using for postgresql - pgadmin.. |
#7
| |||
| |||
|
|
You don't need to putty into the box to use pgAdmin, you just tell pgAdmin the ip address, user (postgres), and password (unless it's trusted). This works as long as you've allowed access from your remote ip address eg in /data/pg_hba.conf you might have something like this host all all 24.233.244.45 255.255.255.255 trust this line trusts all users connecting from 24.233.244.45, so for example pgAdmin could gain db access. No Cygwin necessary for this situation? No cygwin needed. |
|
Can the denizens of this group enlighten me about what the advantages of Python are, versus Perl ? "python" is more likely to pass unharmed through your spelling |
#8
| |||
| |||
|
|
However, in that case the DB connection will _not_ be through ssh, so it will be unencrypted and insecure. From Mike's initial mail I got the impression that he wanted the connection to the PostgreSQL server to go through ssh (which is basically a good thing, because you get ssh's authentication and encryption features). |
#9
| |||
| |||
|
|
You don't need to putty into the box to use pgAdmin, you just tell pgAdmin the ip address, user (postgres), and password (unless it's trusted). This works as long as you've allowed access from your remote ip address eg in /data/pg_hba.conf you might have something like this host all all 24.233.244.45 255.255.255.255 trust this line trusts all users connecting from 24.233.244.45, so for example pgAdmin could gain db access. No Cygwin necessary for this situation? No cygwin needed. |
|
Can the denizens of this group enlighten me about what the advantages of Python are, versus Perl ? "python" is more likely to pass unharmed through your spelling |
#10
| |||
| |||
|
|
[...] Example: First, set up the tunnel in one terminal... ssh -L 4001:remotehost:5432 user@remotehost Then, in another terminal, use psql to connect to the local port (4001) specified in the ssh command: psql -h localhost -p 4001 mydatabase |
|
Assuming this works, can one then use pgaccess to to "tunnel" through the ssh tunnel? Is just changing the port to 4001 instead of 5432 enough to get access to the remote db through pgaccess' login screen? |
![]() |
| Thread Tools | |
| Display Modes | |
| |