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 1jyKzq-00016S-91 for pgsql-admin@arkaria.postgresql.org; Wed, 22 Jul 2020 20:05:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jyKzo-0003Tk-U7 for pgsql-admin@arkaria.postgresql.org; Wed, 22 Jul 2020 20:05:44 +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 1jyKzo-0003R9-K7 for pgsql-admin@lists.postgresql.org; Wed, 22 Jul 2020 20:05:44 +0000 Received: from mail-ot1-x341.google.com ([2607:f8b0:4864:20::341]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jyKzi-0003Kb-1r for pgsql-admin@lists.postgresql.org; Wed, 22 Jul 2020 20:05:43 +0000 Received: by mail-ot1-x341.google.com with SMTP id n24so2682360otr.13 for ; Wed, 22 Jul 2020 13:05:37 -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=TPZVRR4FWFhn36hiXggg8of8FtC8sSfqiR2BsDGdhVE=; b=k1nIcXZyOhv/bCzODPWR3ENLtu+YGriZce38sSlbse3jAx1yVwL0Of4p/MD+0j/S2v 7Wc4rDGs/XkXe8trPyvNHgUxbHb//8EXUy31bMk7oZu1RUDFah4NIZVU6lIH1VslA9wD hTtq2BjDSoQwivo+zSzX4SlSceGGwoOm/DwCy7ETAX3cFM2Ts1ElTf8k6Z80miCv198c ymcGxUYq3xo0Ze7N/Og81Ml4xWaUZM9khWp9Q/TzkGfPJf5c9Ae/fSglFQpNpjjof6mg js/2+cSxddfWyUGt2aKWqERaLpxLpYT1aXxKGPpEejNpGBtn98PpkCllQIjuPDraMjlu NlWA== 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=TPZVRR4FWFhn36hiXggg8of8FtC8sSfqiR2BsDGdhVE=; b=QQP3OFJph1lEBvHClhpuno3M7783+nQUHUEW+GIqJMwDmJj7okL7pOhRRsfDsZ6yx3 jddO0+4FJljViTxlKUMsZylsbHZ1PLJPd2pAOKw8H+wXnS3Hb9Xr3F4zAYXIIAyKEdag KjvLNtkJHQxmszxvQhNSMLjWwSJy6alTuqmxkZXVWLJprOiIsvUXQLoBp3s3Fe8TDUW3 g6IyaNfVZZiRfXJpXyBhY17sjbI8ZX9yDITgp4uardAj3I4oZmrteyerrW2YKy7+ebPy XzzfiHDs7uG6CqRcFizn++0gSr7FlyTN+/4Er0ox5E2Gq4pjwGPUqHw4n5iJCbLOn7MP dIcw== X-Gm-Message-State: AOAM531KCmdraFoB8/bDPI6XEGjYm4OAQ1r2qNSo/cLKnDlO4fUDN1JS mvl60dglZUxN/FxWZp8h8RVX75aeDGnXSg== X-Google-Smtp-Source: ABdhPJwCGNa0noPJf19te7kp3t4DRhVgV+eFRq+uRtRUaekHU9yMebC+/ZdjPcG+PQpg1VLYtb32SA== X-Received: by 2002:a9d:600d:: with SMTP id h13mr1459813otj.172.1595448337082; Wed, 22 Jul 2020 13:05:37 -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 i5sm150116ool.1.2020.07.22.13.05.35 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Jul 2020 13:05:36 -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> From: Ron Message-ID: <11e703a3-e948-0cef-e228-e92e9f701262@gmail.com> Date: Wed, 22 Jul 2020 15:05:35 -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: <20200722185541.GE3899@momjian.us> 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/22/20 1:55 PM, Bruce Momjian wrote: > On Mon, Jul 20, 2020 at 03:24:16PM +0200, Paul Förster wrote: >> Hi Vinod, >> >>> On 20. Jul, 2020, at 14:40, vinod kale wrote: >>> >>> Hello Team, >>> >>> I am using postgresql 10.8 version in our prod environment. We take dump backup on daily basis of full database. And this dump backup creates in human readable format. >>> My requirement is backup should creates in encrypted format at the time of pg_dump running. >>> Is there any way or any option available in pg_dump that will creates the backup in encrypted format or any tool available for same. >> sorry, no way. The only way you have is to pipe the output of pg_dump through some encryption tool. pg_dump does not offer to create encrypted dumps directly using some command line option. > Does anyone know why we are getting so many requests for encrypting > dumps all of a sudden? > > July 20 CAD7GeHRZ3tu8y9VG_0juVK3RQq6r+t6HciguEz_C8Eh85Hmq3A@mail.gmail.com > July 10 CALLD-SGTbu0HCW8NGVg+ycC8PKn9opcbN7aw4CvLj3OVC-hw=Q@mail.gmail.com > July 8 CAFiui6G0sgLoURsK61vmiPR1Amd7PQt82cvgdmZ7+ukdsbV1QQ@mail.gmail.com Audit season? -- Angular momentum makes the world go 'round.