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 v2c0usggekg0 for ; Sun, 6 Jan 2013 13:16:31 +0100 (CET) Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [IPv6:2a01:e0c:1:1599::12]) by mail.saout.de (Postfix) with ESMTP for ; Sun, 6 Jan 2013 13:16:31 +0100 (CET) Received: from molly.corsac.net (unknown [78.192.68.46]) by smtp3-g21.free.fr (Postfix) with ESMTP id 1DBC6A6163 for ; Sun, 6 Jan 2013 13:16:26 +0100 (CET) Message-ID: <1357474572.2800.50.camel@scapa> From: Yves-Alexis Perez Date: Sun, 06 Jan 2013 13:16:12 +0100 In-Reply-To: <50E02816.9000001@gmail.com> References: <50DF635C.90003@gmail.com> <20121230083814.GA12005@tansi.org> <5f058e3c77fb70c10ba5e65e077baa3e.squirrel@ssl.verfeiert.org> <20121230102039.GA12533@tansi.org> <50E02816.9000001@gmail.com> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-a0aFHOuZjUZtei14K7ET" Mime-Version: 1.0 Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.0-rc1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Milan Broz Cc: dm-crypt@saout.de --=-a0aFHOuZjUZtei14K7ET Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On dim., 2012-12-30 at 12:40 +0100, Milan Broz wrote: > On 12/30/2012 11:20 AM, Arno Wagner wrote: >=20 > > Milan: I think presence of if_alg.h should be verified in=20 > > the configure script, possibly with a brief explanation what > > the problem is on fail. The compile-error is a bit obscure. >=20 > TBH, I completely forgot to add this... :) >=20 > Committed to git - by default configure fails with > ... > checking linux/if_alg.h usability... no > checking linux/if_alg.h presence... no > checking for linux/if_alg.h... no > configure: error: You need Linux kernel headers with userspace crypto > interface. (Or use --disable-kernel_crypto.) >=20 > The switch --disable-kernel_crypto completely removes support, > so you can compile it with old kernel or without kernel headers. > (But no cipher benchmark and no tcrypt will be available.) Is this really the proper fix? Usually, userland needing headers more recent than what's in linux-libc-dev should embed them, and correctly handle at runtime if the interfaces are available. What happens here if cryptsetup is built on a recent enough kernel where the header is present, and then run on an old kernel? Will it fail gracefully? Regards, --=20 Yves-Alexis --=-a0aFHOuZjUZtei14K7ET Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAABCAAGBQJQ6WsMAAoJEG3bU/KmdcClM0sH/j1lO84Bg1pqt7nFkgL/8mn+ 9PIRLeTtpbxQuVBrkxyq/36Lbqp+QWYrYOR4l+5kQ51AAzC/fc46n/tF/WwQPLFx cf8HuccAsx2ja012KL4U+En/9o1SVyk+2vLVzofiGkEhGgtUnkP/N5vMGdNaGsIa zSvFcP84/Lyej33eHNFdw/9YIcs6GESQOKYtjHNp/HJ0VCbQBeRj0ayN9wEOuX8O V1hTLgquE62yNeRkd5xZmU9Q7sjyFdAC3ZHfRj1s2lFqfzkwc6fvoXkDT6MNUjBE n1UWkgMtwQPZUapSf3aSPlk6YOLZSGRBnO9JE7jaKVrbLsuqtqA3M8CXju7sH9k= =BMHa -----END PGP SIGNATURE----- --=-a0aFHOuZjUZtei14K7ET--