Date: Wed, 3 Nov 2021 14:45:22 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>,
	Yura Sokolov <y.sokolov@postgrespro.ru>, Sasasu <i@sasa.su>,
	Robert Haas <robertmhaas@gmail.com>,
	Andres Freund <andres@anarazel.de>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: XTS cipher mode for cluster file encryption
Message-ID: <20211103184522.GD20998@tamriel.snowman.net>
References: <d85f5865-1f5a-618e-7d92-92914a0f26b1@sasa.su>
 <20211021172812.GZ20998@tamriel.snowman.net>
 <48020c9811b72499aa5c4c4584b34ed33b75d1b0.camel@postgrespro.ru>
 <20211025161227.GE20998@tamriel.snowman.net>
 <741fa2d3752cc9ef958bb36c495fe952459eaff2.camel@postgrespro.ru>
 <20211026194330.GN20998@tamriel.snowman.net>
 <f51aad97-5f3d-0a61-69d9-2c297ea934e1@enterprisedb.com>
 <20211026213930.GA8607@momjian.us>
 <20211101182436.GW20998@tamriel.snowman.net>
 <20211102214903.GA17209@momjian.us>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="fICFoEfxmEe5Oilm"
Content-Disposition: inline
In-Reply-To: <20211102214903.GA17209@momjian.us>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: 
 <https://www.postgresql.org/message-id/20211103184522.GD20998%40tamriel.snowman.net>
Precedence: bulk


--fICFoEfxmEe5Oilm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greetings,

* Bruce Momjian (bruce@momjian.us) wrote:
> On Mon, Nov  1, 2021 at 02:24:36PM -0400, Stephen Frost wrote:
> > I can understand the general idea that we should be sure to engineer
> > this in a way that multiple methods can be used, as surely one day folks
> > will say that AES128 isn't acceptable any more.  In terms of what we'll
> > do from the start, I would think providing the options of AES128 and
> > AES256 would be good to ensure that we have the bits covered to support
> > multiple methods and I don't think that would put us into a situation of
>=20
> My patch supports AES128, AES192, and AES256.

Right, so we're already showing that it's flexible to allow for multiple
encryption methods.  If folks want more then it's on them to research
how they'd work exactly and explain why they'd be useful to add and how
users might make an informed choice (though, again, I don't think we
need to go *too* deep into that as we don't for, eg, pgcrypto, and I
don't believe we've ever heard people complain about that).

Thanks,

Stephen

--fICFoEfxmEe5Oilm
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJhgtjCAAoJEO1sijiDR2RVUFwP/iiDixMvf5WAsUQPqhsrgOMd
Ta8KXER62bvdZ/7W2tH/EfUSI8PKgzt/Izu0RA9WzZU+3d/6uLfMmVDk835qzpyE
Kgzqk58EhERmbvcyBmLj/cdvILlfqwofTBPpOr50/f4dTeSnf7ZxG9sewYcaL/iQ
wiubhzGGM/Dp0UdvtzerjNILUHazo3AKpkkpzh7uL5f1+9llcaxtAyEqZj228ykc
ypj/dZdRevE1C/NkfV0WXQe1eSJuehq7YBpVFfkkkJcgFTDN6O60IcSWn7tlM6k2
TsR0seicVD1YZcS6sZZBMkmRBm2poX9SGTfe61cSqWov/ZwrONmUsSVzW3o5u09p
tBgwL7+xsCpU9OtyrRCQ4HJOWr5vqsIgkfwSS5ffnpH7EGXIYzwk5oHCZV3QPTS+
6PkV8mTWpIBpo9WuDlZRjIOnHS47EQQjlfTu3KWpe6H3MDjz2gRdX3Z9eHo2Bm3I
pA5Ot7jVqHUZnk1EbLn0G1boGzoMQBI2r2BS3MZe+H+4PENah2yOs5XGgXoJBvs4
BTrRnBO+abVCieMqbgjr+Nn51+Lu8UvQzbhUKHkpW1mXbI7n2j4HRiIDx1ahQdEP
/pAZCdlrqiCChCYq0dY3uPTi362i8Me5EgHTRUu9Q4ufXLvwrkdqVXl90lAHwnks
1j8ptu3KAe5LRPSkqvtq
=Jq5G
-----END PGP SIGNATURE-----

--fICFoEfxmEe5Oilm--