From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corsac@debian.org>
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 VWO-BNtWPfoC for <dm-crypt@saout.de>;
 Mon,  7 Jan 2013 07:23:48 +0100 (CET)
Received: from molly.corsac.net (molly.corsac.net [IPv6:2002:4ec0:442e::1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Mon,  7 Jan 2013 07:23:48 +0100 (CET)
Message-ID: <1357539821.2800.67.camel@scapa>
From: Yves-Alexis Perez <corsac@debian.org>
Date: Mon, 07 Jan 2013 07:23:41 +0100
In-Reply-To: <50E9A54F.1060203@gmail.com>
References: <50DF635C.90003@gmail.com> <20121230083814.GA12005@tansi.org>
 <5f058e3c77fb70c10ba5e65e077baa3e.squirrel@ssl.verfeiert.org>
 <20121230102039.GA12533@tansi.org> <50E02816.9000001@gmail.com>
 <1357474572.2800.50.camel@scapa> <50E9A54F.1060203@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256";
 protocol="application/pgp-signature"; boundary="=-zA3JFtldvjPGvMbCoN9B"
Mime-Version: 1.0
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.0-rc1
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de


--=-zA3JFtldvjPGvMbCoN9B
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On dim., 2013-01-06 at 17:24 +0100, Milan Broz wrote:
> > 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.
>=20
> These are two separate problems
> - you need to compile it on system where new header/kernel is not
> available
> - you need to detect that current kernel is not able to use
> userspace crypto API interface (this includes missing module etc.)
>=20
> Both should be handled already.
>=20
> > 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?
>=20
> It should print something like
> ...
> Required kernel crypto interface not available.
> Ensure you have algif_skcipher kernel module loaded.

Good. And what happens if cryptsetup is built on an old box not having
recent enough headers (typically a buildd) but is run on a box with
recent kernels? I guess there's no support, while, when headers are
embedded, they would be available.

Regards,
--=20
Yves-Alexis

--=-zA3JFtldvjPGvMbCoN9B
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)

iQEcBAABCAAGBQJQ6mntAAoJEG3bU/KmdcClE3UH/0ungc/fxYx/Y6GSfAEw/OU0
THMy8pRpPXJbu5A9I/rmWcXSIcl5XeTaCItzpUB77dzErHfvlhqNvNiKOYUoPwun
TfMvWRM1gSdgTbXJ5/S/0O3WIM7jTYkmSvUGEd1+2g95F04R4vBfhW/mj7QzcNU3
6GnIFATwlNdwgykEKHg6njtJbF6J5c3PuGdAb2inP1TWB4aUVxmN99kcCICy/KhI
0ejHFSLxzUHFYNfuahX1YZS6veSWTbJezibyoyMRp/YYJuXBUVt4/qN0dA38UU1u
D1jIyfkYwTK3g+v22PVwwrGiWcH9IpAkQ3lNvNm24mCFem9E9VYcml2UFoMxvbc=
=e3AV
-----END PGP SIGNATURE-----

--=-zA3JFtldvjPGvMbCoN9B--