Linux bluetooth development
 help / color / mirror / Atom feed
From: Brian Gix <brian.gix@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org
Cc: Brian Gix <brian.gix@intel.com>
Subject: [PATCH BlueZ v2 0/1] Allow Non-Ephemeral ECC Key Sets
Date: Fri, 27 Apr 2018 10:10:48 -0700	[thread overview]
Message-ID: <20180427171049.2250-1-brian.gix@intel.com> (raw)

Version 2, to address uninitialized private_key issue, by adding a new
API. This is separates the two major tasks of generating ECC key sets,
which are:

a) Create a Private Key (Only used here when creating Ephemeral set)
b) Create the matching Public Key from the Private Key.

In hindsight, we may have wanted to call the original API something like
ecc_make_keys() or ecc_make_key_set() instead of the singlular ecc_make_key.
Making that change now will require more wide-reaching changes, however. But
I am willing to do it in a v3 if people think it better.

Some minor spelling/capitalization issues were also addressed

Mesh will be the first to use non-Ephemeral keys

Brian Gix (1):
  shared/ecc: Allow pre-composed Private Keys

 src/shared/ecc.c | 42 +++++++++++++++++++++++++++++-------------
 src/shared/ecc.h | 17 ++++++++++++++---
 2 files changed, 43 insertions(+), 16 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-04-27 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 17:10 Brian Gix [this message]
2018-04-27 17:10 ` [PATCH BlueZ v2 1/1] shared/ecc: Allow pre-composed Private Keys Brian Gix
2018-04-30  8:46   ` Marcel Holtmann
2018-04-30 15:47     ` Gix, Brian
2018-04-30  7:19 ` [PATCH BlueZ v2 0/1] Allow Non-Ephemeral ECC Key Sets Luiz Augusto von Dentz

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=20180427171049.2250-1-brian.gix@intel.com \
    --to=brian.gix@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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