All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2 at infradead.org>
To: tpm2@lists.01.org
Subject: Re: [tpm2] Support for EAP-TLS with openssl TPM2 engine
Date: Wed, 13 Mar 2019 16:56:17 -0700	[thread overview]
Message-ID: <81ab32db49bb3586d0fea02ca02aa6723009ef1d.camel@infradead.org> (raw)
In-Reply-To: dd73a4e2-fc1c-d809-8f35-3797fe16ccb3@web.de

[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]

On Sat, 2019-01-12 at 12:59 +0100, huger(a)web.de wrote:
> Hi
> 
> I am working on a plan to operate mobile Linux computers and would like 
> them to use corporate wifi with EAP TLS. Security requires us to safely 
> store the client key. Easiest solution would be in the computer's TPM 
> 2.0 device.
> 
> So far we were not successful trying to set this up with wpa_supplicant 
> and pkcs11 engine. Even if successful a solution with these multiple 
> layers of abstraction is quite complex and therefore might be prone to 
> updates of any of the components.
> 
> So I wonder if there are plans to directly support openssl tpm2 engine?

Here's a quick hack to make it work by abusing the OpenSC engine
config, as a proof of concept. Making it work cleanly so that it can be
merged is left as an exercise for the reader, or perhaps an interested
party in one of the mailing lists I've added to Cc.

I have no idea why wpa_supplicant doesn't call ENGINE_load_dynamic()
for current versions of OpenSSL. That seems to be a bug, which is why
I've removed the #ifdefs around it.

Signed-off-by: David Woodhouse <dwmw2(a)infradead.org> (not that you'd
want to apply it as-is).

diff --git a/src/crypto/tls_openssl.c b/src/crypto/tls_openssl.c
index 705fa29a3..546d3a598 100644
--- a/src/crypto/tls_openssl.c
+++ b/src/crypto/tls_openssl.c
@@ -864,7 +864,7 @@ static int tls_engine_load_dynamic_pkcs11(const char *pkcs11_so_path,
  */
 static int tls_engine_load_dynamic_opensc(const char *opensc_so_path)
 {
-	char *engine_id = "opensc";
+	char *engine_id = "tpm2";
 	const char *pre_cmd[] = {
 		"SO_PATH", NULL /* opensc_so_path */,
 		"ID", NULL /* engine_id */,
@@ -1034,10 +1034,8 @@ void * tls_init(const struct tls_config *conf)
 
 #ifndef OPENSSL_NO_ENGINE
 	wpa_printf(MSG_DEBUG, "ENGINE: Loading dynamic engine");
-#if OPENSSL_VERSION_NUMBER < 0x10100000L
 	ERR_load_ENGINE_strings();
 	ENGINE_load_dynamic();
-#endif /* OPENSSL_VERSION_NUMBER */
 
 	if (conf &&
 	    (conf->opensc_engine_path || conf->pkcs11_engine_path ||
diff --git a/wpa_supplicant/wpa_supplicant.conf b/wpa_supplicant/wpa_supplicant.conf
index 1bd43b226..b3045fb3d 100644
--- a/wpa_supplicant/wpa_supplicant.conf
+++ b/wpa_supplicant/wpa_supplicant.conf
@@ -174,7 +174,7 @@ fast_reauth=1
 # private_key option appear to be a PKCS#11 URI, and these options
 # should not need to be used explicitly.
 # make the opensc engine available
-#opensc_engine_path=/usr/lib/opensc/engine_opensc.so
+opensc_engine_path=/home/dwmw/git/openssl_tpm2_engine/.libs/libtpm2.so
 # make the pkcs11 engine available
 #pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
 # configure the path to the pkcs11 module required by the pkcs11 engine

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]

             reply	other threads:[~2019-03-13 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 23:56 David Woodhouse [this message]
2019-03-14 16:19 [tpm2] Support for EAP-TLS with openssl TPM2 engine Andersen, John
2019-03-14 16:41 David Woodhouse

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=81ab32db49bb3586d0fea02ca02aa6723009ef1d.camel@infradead.org \
    --to=tpm2@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.