Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jyXAQ-0006r3-F3 for pgsql-admin@arkaria.postgresql.org; Thu, 23 Jul 2020 09:05:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jyXAP-0001xW-4R for pgsql-admin@arkaria.postgresql.org; Thu, 23 Jul 2020 09:05:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jyXAO-0001xO-R3 for pgsql-admin@lists.postgresql.org; Thu, 23 Jul 2020 09:05:28 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jyXAM-0006kQ-9z for pgsql-admin@lists.postgresql.org; Thu, 23 Jul 2020 09:05:28 +0000 Received: by mail-ej1-x62d.google.com with SMTP id br7so5568684ejb.5 for ; Thu, 23 Jul 2020 02:05:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ERKAJzYqnkcsS9hfkdI1mk9d/2/ubdNxmKHTygEoqN4=; b=MO1dGnURKvM06dYXBbBt6DbiGI4FeSi0RFC/qX4u42QnbRTSV9K9bQWWGC2xkMFRgn z9B6aittkYTBW6EpcsJ7xSUaUPXJ8KIv/C1q5ed2N25ue+3ITXQMobBLPjQSj9uyWiav eJYPilp+vZR1pd1bKrF+yyx2SeYybXAyWuWUCwGfnQ9YZjAe0s1Os4s+OI8rJ55hVpTD bC2+xVBwnTiyShL/FCwotlryjHrbWiDHHZPgl9XsPrKV1P8nRIjHfylGeBbAg17M4szd tRAApkBzMfyxqoo+WhPFiFBHiXVxb69tj7yMnP7hgQP4AS+4KCvQdh71IW4L571Qs9FG +6mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ERKAJzYqnkcsS9hfkdI1mk9d/2/ubdNxmKHTygEoqN4=; b=l6Q0ixBR8ZpOMJAamV4l31tXVdEK7/rzCBcRFRHf3feFXx5fcbVxDjeNR/0l7vmYnP O6pULlJTHzdnUhfHSH9PNzL6M4xf+g08yps/Am5kRvN1hs6N5+ZZ5fl3a6GPZqO6YOqX 5xI3MthmHtJrj4WUM7RQYMYKDl2RaodJRzz8VtJuUBXMAn45Xl16XE1U3SsGwq/N8Ulc 60+Hr5vzFayl4zAn3oueeSMLkq8HFJu2bOBiTK4vnXbnZRkbiIFmBnKTuOpO98yIWbhp DmRXTs6z0mCvwk5HtUrORHUH6ogzIS0VBNGW2qfFae3De+nHwC4hLXyorBBtsAKRIrVW ATJQ== X-Gm-Message-State: AOAM531IL97dFet2iqUoqBLgjVBeDgeDRtDNx+PCtzY8aaVzNZuLBcIy PKrB5anGctzAY+f2ChGNzkA= X-Google-Smtp-Source: ABdhPJxOoIamZLad67FZ31l1mmt2kwafDOwSy+nekDbP+MAHGYJs6A2grNMnBLLCjFqtBs0+BIlQ5g== X-Received: by 2002:a17:906:3e54:: with SMTP id t20mr3281651eji.471.1595495123989; Thu, 23 Jul 2020 02:05:23 -0700 (PDT) Received: from [192.168.1.8] (241-57-239-77.dyn.cable.fcom.ch. [77.239.57.241]) by smtp.gmail.com with ESMTPSA id x16sm1642280edr.52.2020.07.23.02.05.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Jul 2020 02:05:23 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) Subject: Re: Encryption in pg_dump From: =?utf-8?Q?Paul_F=C3=B6rster?= In-Reply-To: Date: Thu, 23 Jul 2020 11:05:19 +0200 Cc: Ron , pgsql-admin@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <0EF8B591-3363-4D66-AEB8-CC1F34A53DD7@gmail.com> References: <2BCA8D4B-E94D-4F2F-99A5-D783912A1CDF@gmail.com> <20200722185541.GE3899@momjian.us> <6D40812C-3F42-41A2-A548-4EC7754DF473@gmail.com> <87zh7qbxqk.fsf@gmail.com> <4DCA85A3-B307-48E8-9B30-0D8E2E4911D2@gmail.com> To: Tal Glo X-Mailer: Apple Mail (2.3608.120.23.2.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi Tal, > On 23. Jul, 2020, at 10:27, Tal Glo wrote: > There is a way to implement full homomorphic encryption (FHE) with = Postgres. ok. > I've used a relatively old version (2.3.1) of Microsoft's SEAL library = in my University project for that. I don't know about Windows but I assume, Linux would be similar? > 2. Handling queries related to FHE encrypted attributes on the server = side requires an implementation of own C language functions. we don't do that. Also, we have third party applications. In case they = need to be modified, this is impossible. > It's not always a good Idea to say that something cannot be done or = that some one needs to be replaced. Sometimes it's worth to develop some = new process, based on a mixture of available technologies out there. right, but only if it makes sense. To put a wallet in the file system = and its key right next to it does not make sense but only serves to make = IT heads and security "gurus" go quiet. In these cases, only replacing = them by competent ones helps. Cheers, Paul=