summaryrefslogtreecommitdiffstats
path: root/crypto/asymmetric_keys/pkcs7_parser.c
diff options
context:
space:
mode:
authorDavid Woodhouse <David.Woodhouse@intel.com>2015-07-20 21:16:31 +0100
committerDavid Howells <dhowells@redhat.com>2015-08-07 16:26:14 +0100
commit99d27b1b52bd5cdf9bd9f7661ca8641e9a1b55e6 (patch)
tree8525b8bd99f20016d7e893fa4218951a0b249364 /crypto/asymmetric_keys/pkcs7_parser.c
parentfb1179499134bc718dc7557c7a6a95dc72f224cb (diff)
downloadop-kernel-dev-99d27b1b52bd5cdf9bd9f7661ca8641e9a1b55e6.zip
op-kernel-dev-99d27b1b52bd5cdf9bd9f7661ca8641e9a1b55e6.tar.gz
modsign: Add explicit CONFIG_SYSTEM_TRUSTED_KEYS option
Let the user explicitly provide a file containing trusted keys, instead of just automatically finding files matching *.x509 in the build tree and trusting whatever we find. This really ought to be an *explicit* configuration, and the build rules for dealing with the files were fairly painful too. Fix applied from James Morris that removes an '=' from a macro definition in kernel/Makefile as this is a feature that only exists from GNU make 3.82 onwards. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'crypto/asymmetric_keys/pkcs7_parser.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud