From: Tim Cross <theophilusx@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Encryption in pg_dump
Date: Thu, 23 Jul 2020 15:34:44 +1000
Message-ID: <87zh7qbxqk.fsf@gmail.com> (raw)
In-Reply-To: <6D40812C-3F42-41A2-A548-4EC7754DF473@gmail.com>
References: <CAD7GeHRZ3tu8y9VG_0juVK3RQq6r+t6HciguEz_C8Eh85Hmq3A@mail.gmail.com>
<2BCA8D4B-E94D-4F2F-99A5-D783912A1CDF@gmail.com>
<20200722185541.GE3899@momjian.us>
<6D40812C-3F42-41A2-A548-4EC7754DF473@gmail.com>
Paul Förster <paul.foerster@gmail.com> writes:
> Hi Bruce,
>
>> On 22. Jul, 2020, at 20:55, Bruce Momjian <bruce@momjian.us> wrote:
>>
>> Does anyone know why we are getting so many requests for encrypting
>> dumps all of a sudden?
>
> probably because a) people don't read past posts and b) more and more IT heads decide that *everything*, be it internal to the company or not, has to be encrypted.
>
Yes, I think the IT heads issue is the primary driver - combined with
very poor understanding of information security at senior levels and a
huge growth of poor quality and 'snake oil salesmen' in the IT security space
due to the amount of money ill informed senior managers are throwing at
what they think is a technical problem which usually is in fact a
business process problem.
--
Tim Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: theophilusx@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Encryption in pg_dump
In-Reply-To: <87zh7qbxqk.fsf@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox