linux-kernel - [GIT PULL] KEYS: More fixes for next branch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 06 Nov 2013 15:25:29 +0000
From:	David Howells <dhowells@...hat.com>
To:	jmorris@...ei.org
cc:	dhowells@...hat.com, sgallagh@...hat.com, rdunlap@...radead.org,
	keyrings@...ux-nfs.org, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [GIT PULL] KEYS: More fixes for next branch


Hi James,

Here are another couple of fixes.  Could you apply them to your next branch?

David
---
The following changes since commit 217091dd7a7a1bdac027ddb7c5a25f6ac0b8e241:

  ima: define '_ima' as a builtin 'trusted' keyring (2013-10-31 20:20:48 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git keys-devel

for you to fetch changes up to fbf8c53f1a2ac7610ed124043600dc074992e71b:

  KEYS: Fix UID check in keyctl_get_persistent() (2013-11-06 14:01:51 +0000)

----------------------------------------------------------------
(from the branch description for keys-devel local branch)

clone of "master"
----------------------------------------------------------------
David Howells (2):
      KEYS: The RSA public key algorithm needs to select MPILIB
      KEYS: Fix UID check in keyctl_get_persistent()

 crypto/asymmetric_keys/Kconfig | 1 +
 security/keys/persistent.c     | 6 ++----
 2 files changed, 3 insertions(+), 4 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/