On Thu, Oct 23, 2014 at 12:35:29PM -0400, John Johansen wrote:
> From e81978b2341136b8abdd3669f011c053309a5129 Mon Sep 17 00:00:00 2001
> From: John Johansen
> Date: Thu, 23 Oct 2014 12:33:08 -0400
> Subject: [PATCH] apparmor: add parameter to control whether policy hashing is
> used
>
> v2. Add
On 2014-10-23 12:35:29, John Johansen wrote:
> From e81978b2341136b8abdd3669f011c053309a5129 Mon Sep 17 00:00:00 2001
> From: John Johansen
> Date: Thu, 23 Oct 2014 12:33:08 -0400
> Subject: [PATCH] apparmor: add parameter to control whether policy hashing is
> used
>
> v2. Add kconfig option to
>From e81978b2341136b8abdd3669f011c053309a5129 Mon Sep 17 00:00:00 2001
From: John Johansen
Date: Thu, 23 Oct 2014 12:33:08 -0400
Subject: [PATCH] apparmor: add parameter to control whether policy hashing is
used
v2. Add kconfig option to set default parameter value
Signed-off-by: John Johansen
On Thu, Oct 23, 2014 at 11:51:30AM -0400, John Johansen wrote:
> From 0c0a584c0d073a51e2e8b4c23e7c96f1d3abc358 Mon Sep 17 00:00:00 2001
> From: John Johansen
> Date: Wed, 22 Oct 2014 18:04:34 -0400
> Subject: [PATCH] apparmor: add parameter to control whether policy hashing is
> used
>
> Signed-
On 2014-10-23 11:51:30, John Johansen wrote:
> From 0c0a584c0d073a51e2e8b4c23e7c96f1d3abc358 Mon Sep 17 00:00:00 2001
> From: John Johansen
> Date: Wed, 22 Oct 2014 18:04:34 -0400
> Subject: [PATCH] apparmor: add parameter to control whether policy hashing is
> used
>
> Signed-off-by: John Johan
On 2014-10-23 11:50:28, Seth Arnold wrote:
> On Thu, Oct 23, 2014 at 11:21:22AM -0400, Tyler Hicks wrote:
> > The AppArmor profile hashing feature, configured by
> > CONFIG_SECURITY_APPARMOR_HASH, uses SHA-1 as the hashing algorithm and
> > selects CRYPTO_SHA1. However, by depending on CRYPTO, inst
>From 0c0a584c0d073a51e2e8b4c23e7c96f1d3abc358 Mon Sep 17 00:00:00 2001
From: John Johansen
Date: Wed, 22 Oct 2014 18:04:34 -0400
Subject: [PATCH] apparmor: add parameter to control whether policy hashing is
used
Signed-off-by: John Johansen
---
security/apparmor/include/apparmor.h | 1 +
secu
On Thu, Oct 23, 2014 at 11:21:22AM -0400, Tyler Hicks wrote:
> The AppArmor profile hashing feature, configured by
> CONFIG_SECURITY_APPARMOR_HASH, uses SHA-1 as the hashing algorithm and
> selects CRYPTO_SHA1. However, by depending on CRYPTO, instead of
> selecting it, the tristates CRYPTO and CRY
The AppArmor profile hashing feature, configured by
CONFIG_SECURITY_APPARMOR_HASH, uses SHA-1 as the hashing algorithm and
selects CRYPTO_SHA1. However, by depending on CRYPTO, instead of
selecting it, the tristates CRYPTO and CRYPTO_SHA1 could both be
configured as modules. This causes a build err