From: Brian Gix <brian.gix@intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org
Cc: Brian Gix <brian.gix@intel.com>
Subject: [PATCH BlueZ 0/1] shared/ecc: Make ecc_make_key() a stand alone API
Date: Mon, 7 May 2018 15:35:24 -0700 [thread overview]
Message-ID: <20180507223524.32070-2-brian.gix@intel.com> (raw)
In-Reply-To: <20180507223524.32070-1-brian.gix@intel.com>
And correct minor flaws in API descriptions
---
src/shared/ecc.c | 25 +++++++++++++++++--------
src/shared/ecc.h | 4 +++-
2 files changed, 20 insertions(+), 9 deletions(-)
diff --git a/src/shared/ecc.c b/src/shared/ecc.c
index 15f6b8a93..1c1c3446a 100644
--- a/src/shared/ecc.c
+++ b/src/shared/ecc.c
@@ -883,20 +883,29 @@ bool ecc_make_public_key(const uint8_t private_key[32], uint8_t public_key[64])
bool ecc_make_key(uint8_t public_key[64], uint8_t private_key[32])
{
+ struct ecc_point pk;
uint64_t priv[NUM_ECC_DIGITS];
- unsigned int tries = 0;
- bool result = false;
+ unsigned tries = 0;
+
+ do {
+ if (!get_random_number(priv) || (tries++ >= MAX_TRIES))
+ return false;
- for (tries = 0; !result && tries < MAX_TRIES; tries++) {
- if (!get_random_number(priv))
+ if (vli_is_zero(priv))
continue;
- ecc_native2bytes(priv, private_key);
+ /* Make sure the private key is in the range [1, n-1]. */
+ if (vli_cmp(curve_n, priv) != 1)
+ continue;
- result = ecc_make_public_key(private_key, public_key);
- }
+ ecc_point_mult(&pk, &curve_g, priv, NULL, vli_num_bits(priv));
+ } while (ecc_point_is_zero(&pk));
- return result;
+ ecc_native2bytes(priv, private_key);
+ ecc_native2bytes(pk.x, public_key);
+ ecc_native2bytes(pk.y, &public_key[32]);
+
+ return true;
}
bool ecc_valid_public_key(const uint8_t public_key[64])
diff --git a/src/shared/ecc.h b/src/shared/ecc.h
index a88e735c7..8c15e4ee8 100644
--- a/src/shared/ecc.h
+++ b/src/shared/ecc.h
@@ -28,9 +28,11 @@
#include <stdint.h>
/* Create a public key from a private key.
+ *
+ * Inputs:
+ * private_key - Your private key.
*
* Outputs:
- * private_key - Const private key
* public_key - Will be filled in with the public key.
*
* Returns true if the public key was generated successfully, false
--
2.14.3
next prev parent reply other threads:[~2018-05-07 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 22:35 [PATCH BlueZ 0/1] ECC Cleanup Brian Gix
2018-05-07 22:35 ` Brian Gix [this message]
2018-05-30 7:23 ` 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=20180507223524.32070-2-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;
as well as URLs for NNTP newsgroup(s).