Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 70A062E01A1 for ; Mon, 18 Feb 2008 15:39:51 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 61277-01-4 for ; Mon, 18 Feb 2008 15:39:45 -0400 (AST) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.226]) by postgresql.org (Postfix) with ESMTP id 917342E0217 for ; Mon, 18 Feb 2008 15:31:04 -0400 (AST) Received: by wx-out-0506.google.com with SMTP id r21so1427479wxc.28 for ; Mon, 18 Feb 2008 11:31:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=goO4r5L5ouDajqIxoclyOVGdK4aLH1TdjS8yaLG2UcA=; b=D6cPvs4A2XL27miv/5fPJtSthl3Td+QsLmNAj0c3kCvel7WYL6HCzp1kUjUw6HBIIbfnlePSFs5WMz0pF6dok2ksDLC4QvkfpiNQ0Dxqid9voceVLMCWHFHiDU5ZVAFSZvzKWupAAm2b1vxipn5+B95JXAqnSKoEEx78ehxf0iw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=djIGFtH2g27QVN42j9Sq/hDcieOotOS0jG8CxvblSTebjuQk+6DYu2rTkoB8uu8rk0zuhFydBE8SlW4ygu0OMqKOaS22HLGS4sMlf1+TrTJXNqIhjnU38ku1WH4+k0J1Nex5a61cVVIx0AtwUitG5pl4bzlC/FlBgViy2XYfCeI= Received: by 10.141.62.15 with SMTP id p15mr4081380rvk.159.1203363062034; Mon, 18 Feb 2008 11:31:02 -0800 (PST) Received: from ?192.168.1.102? ( [24.7.64.54]) by mx.google.com with ESMTPS id f21sm10690436rvb.15.2008.02.18.11.30.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 18 Feb 2008 11:30:58 -0800 (PST) Message-ID: <47B9DCF1.4090700@gmail.com> Date: Mon, 18 Feb 2008 11:30:57 -0800 From: paul rivers User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Fabio Telles CC: pgsql-admin@postgresql.org Subject: Re: preventing access with psql References: <5764f4b10802181115r26384616od2b74d0958aeded3@mail.gmail.com> In-Reply-To: <5764f4b10802181115r26384616od2b74d0958aeded3@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/198 X-Sequence-Number: 28272 Fabio Telles wrote: > In Oracle, we use the clause 'set role identified by some_password'. > How could I handle these problem. Any clue? > Normally these role passwords in Oracle are used (and stored) on a middle tier, and not put into the hands of the client. So where are you storing this role pass? Compiling it into the app and hoping no one runs strings on it (or whatever level of digging is required)? Paul