From: David Howells <dhowells@redhat.com>
To: keyrings@linux-nfs.org
Cc: Kees Cook <keescook@chromium.org>,
Josh Boyer <jwboyer@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Vivek Goyal <vgoyal@redhat.com>
Subject: [PATCH1/7] X.509: Export certificate parse and free functions
Date: Tue, 08 Jul 2014 14:15:11 +0100 [thread overview]
Message-ID: <20140708131511.28621.24521.stgit@warthog.procyon.org.uk> (raw)
In-Reply-To: <20140708131504.28621.61165.stgit@warthog.procyon.org.uk>
Export certificate parse and free functions for use by modules.
Signed-off-by: David Howells <dhowells@redhat.com>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Josh Boyer <jwboyer@redhat.com>
---
crypto/asymmetric_keys/x509_cert_parser.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/crypto/asymmetric_keys/x509_cert_parser.c b/crypto/asymmetric_keys/x509_cert_parser.c
index 4a8df29..ac72348 100644
--- a/crypto/asymmetric_keys/x509_cert_parser.c
+++ b/crypto/asymmetric_keys/x509_cert_parser.c
@@ -11,6 +11,7 @@
#define pr_fmt(fmt) "X.509: "fmt
#include <linux/kernel.h>
+#include <linux/export.h>
#include <linux/slab.h>
#include <linux/err.h>
#include <linux/oid_registry.h>
@@ -52,6 +53,7 @@ void x509_free_certificate(struct x509_certificate *cert)
kfree(cert);
}
}
+EXPORT_SYMBOL_GPL(x509_free_certificate);
/*
* Parse an X.509 certificate
@@ -97,6 +99,7 @@ error_no_ctx:
error_no_cert:
return ERR_PTR(ret);
}
+EXPORT_SYMBOL_GPL(x509_cert_parse);
/*
* Note an OID when we find one for later processing when we know how
next prev parent reply other threads:[~2014-07-08 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 13:15 [PATCH 0/7] KEYS: PKCS#7 asymmetric key parser David Howells
2014-07-08 13:15 ` David Howells [this message]
2014-07-08 13:15 ` [PATCH2/7] PKCS#7: Implement a parser [RFC 2315] David Howells
2014-07-08 13:15 ` [PATCH3/7] PKCS#7: Digest the data in a signed-data message David Howells
2014-07-08 13:15 ` [PATCH4/7] PKCS#7: Find the right key in the PKCS#7 key list and verify the signature David Howells
2014-07-08 13:15 ` [PATCH5/7] PKCS#7: Verify internal certificate chain David Howells
2014-07-08 13:15 ` [PATCH6/7] PKCS#7: Find intersection between PKCS#7 message and known, trusted keys David Howells
2014-07-08 13:15 ` [PATCH7/7] PKCS#7: Provide a key type for testing PKCS#7 David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140708131511.28621.24521.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jwboyer@redhat.com \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®