Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 55BE59FB24D for ; Mon, 23 Jul 2007 11:26:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 48627-01 for ; Mon, 23 Jul 2007 11:26:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2612D9FB1BB for ; Mon, 23 Jul 2007 11:26:28 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l6NEQPR2024057; Mon, 23 Jul 2007 10:26:25 -0400 (EDT) To: "Thiago Maluf" cc: pgsql-admin@postgresql.org Subject: Re: Disable access shell command in psql In-reply-to: References: Comments: In-reply-to "Thiago Maluf" message dated "Mon, 23 Jul 2007 10:59:17 -0300" Date: Mon, 23 Jul 2007 10:26:25 -0400 Message-ID: <24056.1185200785@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/245 X-Sequence-Number: 26226 "Thiago Maluf" writes: > I have one database server with postgresql 8.1 and I discovered yesterday > one security problem. > When I access my server with thought psql I have the possibility execute > command in my server using "\!" or write one file using "\e". These are done on the client side, not the server side. There is no security issue here, because psql's user could equally well do the same things without using psql. regards, tom lane