From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qz1-WN_yWnUj for ; Thu, 14 Mar 2013 21:35:20 +0100 (CET) Received: from gerolde.archlinux.org (gerolde.archlinux.org [66.211.214.132]) by mail.saout.de (Postfix) with ESMTP for ; Thu, 14 Mar 2013 21:35:20 +0100 (CET) Received: from [134.61.78.153] (78-153.eduroam.rwth-aachen.de [134.61.78.153]) by gerolde.archlinux.org (Postfix) with ESMTPSA id 41FBC900B0 for ; Thu, 14 Mar 2013 12:20:53 -0400 (EDT) Message-ID: <5141F8E1.6060001@archlinux.org> Date: Thu, 14 Mar 2013 17:20:49 +0100 From: =?ISO-8859-15?Q?Thomas_B=E4chler?= MIME-Version: 1.0 References: <40727.130.226.154.66.1362921572.squirrel@lavabit.com> <20130310192312.GA9676@tansi.org> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----enig2FLULVKVUQMJOFXERFPFF" Subject: Re: [dm-crypt] hardware encryption List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2FLULVKVUQMJOFXERFPFF Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Am 13.03.2013 22:45, schrieb lxnf98mm@gmail.com: > Can dm-crypt make use of the encryption capabilities of the cpu > I am probably not asking the right question but gotta start somewhere >=20 > Richard In short, dm-crypt uses whatever the kernel's crypto API provides. For details on that, refer to the configuration of your kernel. ------enig2FLULVKVUQMJOFXERFPFF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJRQfjjAAoJEChPw0yOSxolWxEQAKiuPkRU2/Hz1NYIbZSPo6WE tVj728gBFnv68gpbfvt4RmcBjhzTUHNa6VVaEi8wbqXNsSPL7FQX31xS0jbdjw2m hDQyAHrNL8SwIK8hEGIKKSTTcSvZDtJXipnKYWR8S5bVyKXF4oyk6XKZEkkZ/h7V tuRi/Dr30BrmpTSLeUyfJN9hFBAi9skQVQYuiOp5OIGJznDcyEIXWMxTkYMxH2B5 G3+AU4xR8rdI8sKCIf3B3PpmP8gbSStTqkPxMRfnf/yKyKaIhm+XClejNBULV0Ch hbuFKpsloOtolOuffxkQ03jlOISWPcSbQQ843FbTbnu+xX+QIfH+IsefgMfp7zW5 jbaL+9lxO7c2NDAMTRjzm89J3qbZ6vzV2vdhpSE498M0EhHBgg6rTmp37hWGYquK EAbGI6EYT4duXR3Z9zkDf+2Ng/Lmm7NLE29q/Ksu/z1ODlMBXoAAs7Hs1hVexzGf GfaA4NIUM7iju2x6DO9iXFhqAqzr8FyR4nmdaXOdhYbXVKqs9p+SKQdFKpFOmtmr b+OV9iEj/5Z+b4NskhMfiaWY83SELYbgWVAxRIATwqLIdzqWnwlnXPOcoYh9CRpQ BHn1hauwjZyOYcY7A/4dFTDpeUPljwaLi1rocAdz5kFS0+AY50s216HEMO/jyKHo oHn3HMad3uLyQiCC7MMp =KeZp -----END PGP SIGNATURE----- ------enig2FLULVKVUQMJOFXERFPFF--