Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1301284
| From | Valdis.Kletnieks@vt.edu |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: next-20151231 - aes crypto algorithm went missing? |
| Date | 2016-01-05 07:10 +0100 |
| Message-ID | <qNsYF-6lk-1@gated-at.bofh.it> (permalink) |
| References | <qMJyz-1gX-29@gated-at.bofh.it> <qMO5c-46P-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Sun, 03 Jan 2016 11:20:03 +0100, Milan Broz said: > On 01/03/2016 06:34 AM, Valdis Kletnieks wrote: > > So booting into a next-20151222 kernel, I can mount an external drive > > that uses cryptLuks. I try -1231, and I get this failure: > > > > Failed to setup dm-crypt key mapping for device /dev/sdb2. > > Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for more info). > > > > Tracked it down to this difference in /proc/crypto between the 12/22 and 12/31: > > ... > > This ringing any bells, before I start the New Year with a bisect? :) > > Perhaps see the discussion in thread > [PATCH v2] crypto: algif_skcipher - Require setkey before accept(2) > > Could you try to revert this patch? > http://git.kernel.org/cgit/linux/kernel/git/next/linux-next-history.git/commit/crypto?id=9f47e11b9e3169ff4cb35b3cdac0e0f7c2fcfe27 Confirming that this patch reverts cleanly for me, and makes cryptsetup happy again on next-20151231.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
next-20151231 - aes crypto algorithm went missing? Valdis Kletnieks <Valdis.Kletnieks@vt.edu> - 2016-01-03 06:40 +0100
Re: next-20151231 - aes crypto algorithm went missing? Milan Broz <gmazyland@gmail.com> - 2016-01-03 11:30 +0100
Re: next-20151231 - aes crypto algorithm went missing? Valdis.Kletnieks@vt.edu - 2016-01-05 07:10 +0100
csiph-web