From: | Jeff Amiel <jamiel(at)istreamimaging(dot)com> |
---|---|
To: | Paul Tillotson <pntil(at)shentel(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgres "on in the internet" |
Date: | 2004-09-03 12:41:30 |
Message-ID: | 4138667A.10809@istreamimaging.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Well...if it's truly a client/server app, why not have the client app
talk to the server who actually executes the SQL. That way no remote
access to the database is required.
IMHO, it's a 'bad thing' to have your database exposed to the internet....
Jeff Amiel
Paul Tillotson wrote:
> At my company we are looking at deploying clients for our
> client/server app outside our firewall, which will then require our
> postgres box to be internet-accessible.
> Does anyone out there have experience with this or recommended best
> practices? We have been looking at either (a) tunnelling everything
> over ssh, or (b) just making sure that users have "strong" passwords
> and requiring "md5" authentication in pg_hba.conf.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Suresh Tri | 2004-09-03 13:49:47 | Overloading || ( text,text ) operator |
Previous Message | Martin Münstermann | 2004-09-03 11:17:47 | symbol name clash with libpq.so |