Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 3AC30633D87 for ; Fri, 19 Jun 2009 10:36:51 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 82611-05 for ; Fri, 19 Jun 2009 10:36:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from titania.wxnz.net (titania.wxnz.net [58.28.4.13]) by mail.postgresql.org (Postfix) with ESMTP id 10836633D2B for ; Fri, 19 Jun 2009 10:36:49 -0300 (ADT) Received: from gonzo (ip-118-90-143-151.xdsl.xnet.co.nz [118.90.143.151]) by titania.wxnz.net (Postfix) with ESMTP id 1574F1DB81CC for ; Sat, 20 Jun 2009 01:36:45 +1200 (NZST) Received: from news by gonzo with local (Exim 4.69) (envelope-from ) id 1MHeGn-0005xP-41 for pgsql-sql@postgresql.org; Sat, 20 Jun 2009 01:36:41 +1200 To: pgsql-sql@postgresql.org Path: not-for-mail From: Jasen Betts Newsgroups: gmane.comp.db.postgresql.sql Subject: Re: SQL File in encrypted form Date: 19 Jun 2009 13:36:40 GMT Organization: Dis (not Dat) Organisation Lines: 24 Message-ID: References: <000001c9f0ca$7935f890$6ba1e9b0$@com> NNTP-Posting-Host: localhost Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: reversiblemaps.ath.cx 1245418600 22096 127.0.0.1 (19 Jun 2009 13:36:40 GMT) X-Face: ?)Aw4rXwN5u0~$nqKj`xPz>xHCwgi^q+^?Ri*+R(&uv2=E1Q0Zk(>h!~o2ID@6{uf8s; a +M[5[U[QT7xFN%^gR"=tuJw%TXXR'Fp~W; (T"1(739R%m0Yyyv*gkGoPA.$b,D.w:z+<'"=-lVT?6 {T?=R^:W5g|E2#EhjKCa+nt":4b}dU7GYB*HBxn&Td$@f%.kl^:7X8rQWd[NTc"P"u6nkisze/Q; 8 "9Z{peQF,w)7UjV$c|RO/mQW/NMgWfr5*$-Z%u46"/00mx-,\R'fLPe.)^ User-Agent: slrn/pre1.0.0-2 (Linux) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200906/89 X-Sequence-Number: 32694 On 2009-06-19, Jyoti Seth wrote: > This is a multipart message in MIME format. > > ------=_NextPart_000_0001_01C9F0F8.92EE3490 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: 7bit > > Hi All, > > > > I want to send the sql script file to a client but wants to hide the details > in it. Can I send the sql script file in encrypted form which they can > execute but can't view the details. only by building it into an encrypted executable. be sure to use SSL on the database connection. or possibly you could write a backend extension (stored procedure writtern in C, Java, or other compiled language) that does decrypting and execution in a single step and use that. what sort of things are you trying to hide?