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 1jyXHJ-00071f-Mf for pgsql-admin@arkaria.postgresql.org; Thu, 23 Jul 2020 09:12:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jyXHI-0001Ni-1Y for pgsql-admin@arkaria.postgresql.org; Thu, 23 Jul 2020 09:12:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jyXHH-0001NZ-OQ for pgsql-admin@lists.postgresql.org; Thu, 23 Jul 2020 09:12:35 +0000 Received: from mail-ot1-x332.google.com ([2607:f8b0:4864:20::332]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jyXHF-0002FF-B0 for pgsql-admin@lists.postgresql.org; Thu, 23 Jul 2020 09:12:34 +0000 Received: by mail-ot1-x332.google.com with SMTP id h1so3827516otq.12 for ; Thu, 23 Jul 2020 02:12:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=v6jMEFqoVUoOc/kMAP3QqAgS1EVHrUHhTIJki+DYWLY=; b=KqE3mcvVPSLfBsi4NWR5saz9ufAxK6yl46DtVgSWMMMGyN01smkCzFGT4IzX7r6LP9 G+0aBePKjTLqKI/Ne82y66FK4fRQctetpuEBSebOrTqiUIAQuyJoLkdQAUQiMdh2tpDd V/R/aWvOwe15BquqaTlC5FEqn3r2shc8bRhXkkhLfKJ7W64GfW4dnOapacn5zc6QsEba 9nl6YwilOzziftCqHUvB0YdBo2/48kzoXekYmp+AVL87lpLjtSEmfY5LhjQ+22Re2Lo3 sV08Ta3U3nrky6BPUQgD0YNpah4uiDyRO9+NmNVngbtrdyEyNluM/5pkjX+hm4K0d9qK /yMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=v6jMEFqoVUoOc/kMAP3QqAgS1EVHrUHhTIJki+DYWLY=; b=C9zENIv+E5ByF2M2MeF65EpXb7WqQ8cxVMeHXUqNzd9FZ5f0Gj1mSTGjz+jhOHRE6G PoVjw1llovhpp6mMUOmfwx3zmTjOzL9IyOjv432JSy9SzQfmQcWGXu64gFloKUiXnFVD TrB7NEzfcpVOrHEwm6XoM8eUxUC/Wu6bVYuta7gnzZ++9Noua5RY5MeMsfNwalSR2fgZ SUvCJC2qjUvQNhA1mhaSqkTsYw+aBnGGLqKxwf2njL4Ee32P0jaPlrN10WCtfdVtPap/ O6//leWu+/ZVllv2igmYbPfgN3cc0Rt5BCacildih+7oYMvaz8bkNinXipi9qlWTTEJ5 Gd6g== X-Gm-Message-State: AOAM533ngipOeyx/stBTQtcUeFcNF/F2xmbvTY5r/IPWzbLUh5RZFpqZ 9doK5fsnNyK46JBj760xfmrt/S9Od9ddzw== X-Google-Smtp-Source: ABdhPJz7O/LZaBkPsiTzsrc27xH3JsA40fnnRFF0SPJR14T0eUcANGNU7ZdEZGMmZMe3lVGg0LJmcQ== X-Received: by 2002:a05:6830:1543:: with SMTP id l3mr3256768otp.84.1595495551885; Thu, 23 Jul 2020 02:12:31 -0700 (PDT) Received: from [192.168.1.10] (ip70-186-126-197.no.no.cox.net. [70.186.126.197]) by smtp.googlemail.com with ESMTPSA id y18sm532963ooa.16.2020.07.23.02.12.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 23 Jul 2020 02:12:31 -0700 (PDT) Subject: Re: Encryption in pg_dump To: pgsql-admin@lists.postgresql.org 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> <0EF8B591-3363-4D66-AEB8-CC1F34A53DD7@gmail.com> From: Ron Message-ID: <16c2a4f1-5167-a4f8-ab61-b0e083c94ee5@gmail.com> Date: Thu, 23 Jul 2020 04:12:30 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <0EF8B591-3363-4D66-AEB8-CC1F34A53DD7@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 7/23/20 4:05 AM, Paul Förster wrote: > 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. That was my first thought, too.  We mostly run 3rd party applications, with very little home-grown.  TDE (transparent data encryption) is the only reasonable work-around. >> 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. Which is as unlikely as getting all 3rd party vendors to implement application-level encryption. -- Angular momentum makes the world go 'round.