TPM2 (Trusted Platform Module) userspace development
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock at linux.intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] TPM2TSS engine for OpenSSL
Date: Tue, 28 Aug 2018 16:30:09 +0100	[thread overview]
Message-ID: <830ea19fdb26bb76cc12f8ff585baafb1dffb9fb.camel@linux.intel.com> (raw)
In-Reply-To: 9F48E1A823B03B4790B7E6E69430724D014263A805@exch2010c.sit.fraunhofer.de

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

On Tue, 2018-08-28 at 14:58 +0000, Fuchs, Andreas wrote:
> Hi Joshua,
> 
> the engine is tested against openssl 1.0.2 and 1.1.0 using travis ci,
> see 
> https://github.com/tpm2-software/tpm2-tss-engine/blob/master/.travis.yml
> 
> The fedora-info looks strange, since is says "No such file or
> directory".
> Could you check that  /usr/local/lib/openssl/engines/tpm2tss.so
> actually exists ?

It doesn't, I do have libtpm2tss.so (same on my Ubuntu 16.04.5 VM
though).
However, if I link the libtpm2tss.so -> tpm2tss.so the engine is picked
up:
$ sudo ln -s /usr/local/lib/openssl/engines/libtpm2tss.so
/usr/local/lib/openssl/engines/tpm2tss.so
$ OPENSSL_ENGINES=/usr/local/lib/openssl/engines openssl engine -t -c
tpm2tss
(tpm2tss) TPM2-TSS engine for OpenSSL
 [RSA, RAND]
     [ available ]

or indeed if I use libtpm2tss as the engine name:

$ OPENSSL_ENGINES=/usr/local/lib/openssl/engines openssl engine -t -c
libtpm2tss
(libtpm2tss) TPM2-TSS engine for OpenSSL
Loaded: (tpm2tss) TPM2-TSS engine for OpenSSL
 [RSA, RAND]
     [ available ]

Thanks,

Joshua


             reply	other threads:[~2018-08-28 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 15:30 Joshua Lock [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-30  8:16 [tpm2] TPM2TSS engine for OpenSSL Fuchs, Andreas
2018-08-30  1:19 Philip Tricca
2018-08-28 15:07 Philip Tricca
2018-08-28 14:58 Fuchs, Andreas
2018-08-28 14:45 Joshua Lock
2018-06-13 10:16 Fuchs, Andreas

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=830ea19fdb26bb76cc12f8ff585baafb1dffb9fb.camel@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox