summaryrefslogtreecommitdiff
path: root/crypto/crypto_wq.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2013-11-23 16:38:17 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2013-11-23 16:38:17 -0800
commit82203623f6f9190ceb1b0730ebf4804390e88c9f (patch)
treef8fe5d96d27247bc350dc6d7bc4a0b31f393d156 /crypto/crypto_wq.c
parent5cc5f78dc9afde9ef8bde7a423f5de0eaf6b9a85 (diff)
downloadlinux-crypto-82203623f6f9190ceb1b0730ebf4804390e88c9f.tar.gz
linux-crypto-82203623f6f9190ceb1b0730ebf4804390e88c9f.zip
Revert "KEYS: verify a certificate is signed by a 'trusted' key"
This reverts commit 5f8e45ca1ff758063de09b9438242c98ec34fad1, which caused the following build errors: crypto/asymmetric_keys/x509_public_key.c: In function ‘x509_key_preparse’: crypto/asymmetric_keys/x509_public_key.c:237:35: error: ‘system_trusted_keyring’ undeclared (first use in this function) ret = x509_validate_trust(cert, system_trusted_keyring); ^ crypto/asymmetric_keys/x509_public_key.c:237:35: note: each undeclared identifier is reported only once for each function it appears in reported by Jim Davis. Mimi says: "I made the classic mistake of requesting this patch to be upstreamed at the last second, rather than waiting until the next open window. At this point, the best course would probably be to revert the two commits and fix them for the next open window" Reported-by: Jim Davis <jim.epost@gmail.com> Acked-by: Mimi Zohar <zohar@linux.vnet.ibm.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'crypto/crypto_wq.c')
0 files changed, 0 insertions, 0 deletions