From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: intel-sgx-kernel-dev@lists.01.org, platform-driver-x86@vger.kernel.org
Subject: Re: [intel-sgx-kernel-dev] [PATCH RFC v3 10/12] intel_sgx: in-kernel launch enclave
Date: Tue, 14 Nov 2017 16:22:50 +0200 [thread overview]
Message-ID: <20171114142250.shjb5arlyomewlis@linux.intel.com> (raw)
In-Reply-To: <1510171646.4659.5.camel@intel.com>
On Wed, Nov 08, 2017 at 12:07:26PM -0800, Sean Christopherson wrote:
> On Tue, 2017-10-10 at 17:32 +0300, Jarkko Sakkinen wrote:
> > +static RSA *load_sign_key(const char *path)
> > +{
> > + FILE *f;
> > + RSA *key;
> > +
> > + f = fopen(path, "rb");
> > + if (!f) {
> > + fprintf(stderr, "Unable to open %s\n", path);
> > + return NULL;
> > + }
> > + key = RSA_new();
> > + if (!PEM_read_RSAPrivateKey(f, &key, pem_passwd_cb, NULL))
> > + return NULL;
> > + fclose(f);
> > +
> > + if (BN_num_bytes(key->n) != SGX_MODULUS_SIZE) {
>
> Dereferencing the RSA pointer (key) breaks on OpenSSL 1.1.0 as RSA is now an
> opaque object. It's relatively easy to fudge around the issue, patch below.
>
> https://github.com/openssl/openssl/issues/1491
> https://wiki.openssl.org/index.php/OpenSSL_1.1.0_Changes
>
> > + fprintf(stderr, "Invalid key size %d\n", BN_num_bytes(key-
> > >n));
> > + RSA_free(key);
> > + return NULL;
> > + }
> > +
> > + return key;
> > +}
> > +
>
> diff --git drivers/platform/x86/intel_sgx/le/enclave/sgxsign.c
> drivers/platform/x86/intel_sgx/le/enclave/sgxsign.c
> index 27e8c61d033c..e454dc95f438 100644
> --- drivers/platform/x86/intel_sgx/le/enclave/sgxsign.c
> +++ drivers/platform/x86/intel_sgx/le/enclave/sgxsign.c
> @@ -110,6 +110,17 @@ static int pem_passwd_cb(char *buf, int size, int rwflag,
> void *u)
> return strlen(buf) >= size ? size - 1 : strlen(buf);
> }
>
> +static inline const BIGNUM *get_modulus(RSA *key)
> +{
> +#if OPENSSL_VERSION_NUMBER < 0x10100000L
> + return key->n;
> +#else
> + const BIGNUM *n;
> + RSA_get0_key(key, &n, NULL, NULL);
> + return n;
> +#endif
> +}
> +
> static RSA *load_sign_key(const char *path)
> {
> FILE *f;
> @@ -125,8 +136,9 @@ static RSA *load_sign_key(const char *path)
> return NULL;
> fclose(f);
>
> - if (BN_num_bytes(key->n) != SGX_MODULUS_SIZE) {
> - fprintf(stderr, "Invalid key size %d\n", BN_num_bytes(key->n));
> + if (BN_num_bytes(get_modulus(key)) != SGX_MODULUS_SIZE) {
> + fprintf(stderr, "Invalid key size %d\n",
> + BN_num_bytes(get_modulus(key)));
> RSA_free(key);
> return NULL;
> }
> @@ -511,7 +523,7 @@ int main(int argc, char **argv)
> if (!sign_key)
> goto out;
>
> - BN_bn2bin(sign_key->n, ss.modulus);
> + BN_bn2bin(get_modulus(sign_key), ss.modulus);
>
> if (!measure_encl(argv[1], ss.body.mrenclave))
> goto out;
>
Already sent v5 but I'll put this to v6. Thanks.
/Jarkko
next prev parent reply other threads:[~2017-11-14 14:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 14:32 [PATCH RFC v3 00/12] Intel(R) SGX Driver Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 01/12] intel_sgx: updated MAINTAINERS Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 02/12] x86: add SGX definition to cpufeature Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 03/12] x86: define the feature control MSR's SGX enable bit Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 04/12] x86: define the feature control MSR's SGX launch control bit Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 05/12] x86: add SGX MSRs to msr-index.h Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 06/12] fs/pipe.c: export create_pipe_files() and replace_fd() Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 08/12] intel_sgx: ptrace() support Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 09/12] intel_sgx: driver documentation Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 10/12] intel_sgx: in-kernel launch enclave Jarkko Sakkinen
2017-11-08 20:07 ` [intel-sgx-kernel-dev] " Sean Christopherson
2017-11-14 14:22 ` Jarkko Sakkinen [this message]
2017-10-10 14:32 ` [PATCH RFC v3 11/12] intel_sgx: glue code for in-kernel LE Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 12/12] intel_sgx: update IA32_SGXLEPUBKEYHASH* MSRs Jarkko Sakkinen
[not found] ` <20171010143258.21623-8-jarkko.sakkinen@linux.intel.com>
2017-10-10 15:41 ` [intel-sgx-kernel-dev] [PATCH RFC v3 07/12] intel_sgx: driver for Intel Software Guard Extensions Sean Christopherson
2017-10-11 11:46 ` Jarkko Sakkinen
2017-10-11 15:56 ` Sean Christopherson
2017-10-10 18:26 ` Sean Christopherson
2017-10-13 19:58 ` Jarkko Sakkinen
2017-10-13 20:02 ` Jarkko Sakkinen
2017-10-13 20:08 ` Jarkko Sakkinen
2017-10-13 20:13 ` Jarkko Sakkinen
2017-10-12 16:48 ` Sean Christopherson
2017-10-13 19:16 ` Jarkko Sakkinen
2017-11-02 19:48 ` Sean Christopherson
2017-11-06 7:23 ` Jarkko Sakkinen
2017-11-02 20:10 ` Sean Christopherson
2017-11-06 11:08 ` Jarkko Sakkinen
2017-11-06 11:33 ` Jarkko Sakkinen
2017-11-06 14:56 ` Sean Christopherson
2017-11-08 6:25 ` Jarkko Sakkinen
2017-11-06 11:39 ` Jarkko Sakkinen
2017-11-06 14:54 ` Sean Christopherson
2017-11-07 18:43 ` Jarkko Sakkinen
2017-11-06 15:54 ` Dave Hansen
2017-11-07 18:47 ` Jarkko Sakkinen
2017-11-07 19:05 ` Dave Hansen
2017-11-14 19:33 ` Jarkko Sakkinen
2017-11-14 21:05 ` Jarkko Sakkinen
2017-11-14 21:12 ` Dave Hansen
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=20171114142250.shjb5arlyomewlis@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=intel-sgx-kernel-dev@lists.01.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sean.j.christopherson@intel.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