From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from molly.corsac.net (pic75-3-78-194-244-226.fbxo.proxad.net [78.194.244.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Wed, 3 Feb 2016 15:02:15 +0100 (CET) Message-ID: <1454508127.7684.9.camel@debian.org> From: Yves-Alexis Perez Date: Wed, 03 Feb 2016 15:02:07 +0100 In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-2v5oGONJwSoft72KKWr7" Mime-Version: 1.0 Subject: Re: [dm-crypt] The future of disk encryption with LUKS2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ".. ink .." , "dm-crypt@saout.de" --=-2v5oGONJwSoft72KKWr7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mer., 2016-02-03 at 16:13 +0300, .. ink .. wrote: > I am curious about what problems luks1 current has and how luks2 is > going to fix them but there > seem to be no documentation about luks2 anywhere. Looking at the list archive I found <55DAB73F.2080002@gmail.com>=C2=A0and f= ollowup <20150824115418.GA20268@tansi.org> There's also the wip-luks2 branch at=C2=A0https://gitlab.com/cryptsetup/cry= ptsetup/ tree/wip-luks2 Regards, --=20 Yves-Alexis --=-2v5oGONJwSoft72KKWr7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJWsghfAAoJEG3bU/KmdcClQ6YH/086KNvL9/hM9VxkxfHCz8Bs x4HrCpFxWbuKXosnog6svaroS/5ZFIitgNUUdT4P7Xe6T/A/jTtqCKfOPS6mkR7E +EICCL+oha6j15oi6vhhpZCvtNdHH4KQnp/bU2GlCMrgcsF805p+FYkQrdYTPsHu jLU3+xoq1fMx6MfWkMNmlBLZI0j8h9ivf8e89mXRci6nv0NAEYFBizjJscDylO14 HwruY8dF3BF7XlEaEx+57Ki75gf1a3HDMoOuqEMH7oHiWNd/vWmdiKouOCIvRJXe aLZWfFwWC9NrUV8IfDHZWj4CjbdHzx0oJvENQnENtxSW6H9I8xwOcleX8MeRcZk= =Tnaq -----END PGP SIGNATURE----- --=-2v5oGONJwSoft72KKWr7--