On Sun, Nov 23, 2014 at 12:55:22PM +0100, Christian Kastner wrote: > > I can confirm that is issue exists with 3.17. > > > > The syscall is returning ENOKEY where until 3.16 it was returning EPERM. > > I am now quite certain that the issue is being caused by this kernel > commit in 3.17: > > Commit: a4e3b8d79a5c6d40f4a9703abf7fe3abcc6c3b8d > KEYS: special dot prefixed keyring name bug fix
Except, it fails with earlier kernels too: I tested 3.8 on armhf and 3.11 on amd64 (the latter with config identical to Debian's in all "uninteresting" to me areas). But at least 3.16 is ok. > Either way, I tagged this "sid" as it can only appear with a kernel that > will not be part of Jessie. So that should solve the RC problem, no? Sounds good to me. Meow! -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
