Hi James,
Can you please pull these fixes and send them on upstream:
(1) Reinstate the production of EPERM for key types beginning with '.' in
requests from userspace.
(2) Tidy up the cleanup of PKCS#7 message signed information blocks and fix a
bug this made more obvious.
They will also need merging into security/next so that further patches that
depend on them can be applied.
David
---
The following changes since commit 478d085524c57cf4283699f529d5a4c22188ea69:
Merge tag 'keys-next-20140805' of
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs into next
(2014-08-06 00:52:01 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
tags/keys-fixes-20140916
for you to fetch changes up to cecf5d2e1208da512a4c951c24acd66c54a4d06c:
PKCS#7: Fix the parser cleanup to drain parsed out X.509 certs (2014-09-16
17:29:03 +0100)
----------------------------------------------------------------
(from the branch description for keys-fixes local branch)
Keyrings fixes
Keyrings fixes
----------------------------------------------------------------
David Howells (3):
KEYS: Reinstate EPERM for a key type name beginning with a '.'
PKCS#7: Provide a single place to do signed info block freeing
PKCS#7: Fix the parser cleanup to drain parsed out X.509 certs
crypto/asymmetric_keys/pkcs7_parser.c | 61 +++++++++++++++++++----------------
security/keys/keyctl.c | 2 ++
2 files changed, 35 insertions(+), 28 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
