Received: from waco2.calpha.com (waco2.calpha.com [208.232.233.3]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA2Jh5l48718 for ; Thu, 2 Nov 2000 14:43:05 -0500 (EST) (envelope-from Greg@10happythings.com) Received: from 10happythings.com (gspeegle.t1-s.wireless.calpha.com [63.80.26.25] (may be forged)) by waco2.calpha.com (8.10.1/8.10.1) with ESMTP id eA2Jgfs05155 for ; Thu, 2 Nov 2000 13:42:45 -0600 Message-ID: <3A01C3AA.ACF61B2@10happythings.com> Date: Thu, 02 Nov 2000 13:42:34 -0600 From: Greg Speegle X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: Re: Connecting remotely - multi tier References: <19340927123446.8209@mail.gol.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200011/49 X-Sequence-Number: 85 keke abe wrote: > Adam Lang wrote: > > > Ok... so if I am writing a distributed application in windows that will use > > a Postgresql backend, I should have the client interface another "server" > > application, which will inturn access/retrieve informaton from the database? > > I'd like to know if this kind of layering is mandatory or not. Is it really > unacceptable to expose the Posgresql backend to the rest of the world? Is > there anything that I should be aware of if I let the clients to talk to > the backend directly. > > regards, > abe I'd say it is mandatory. You are opening yourself up as an easy target for hackers if they can go directly to your database. Think about it. If any hole in the database security is discovered, then your goose is cooked right away. Getting the database off the web and behind a firewall should be the least you do. That gives you two levels of protection -- the firewall and the database. Plus, on the postgresql side, it is much easier to have one restricted user account from one specific machine than to try to manage thousands of dynamically created accounts. Just my opinion, of course. Greg Speegle