From f7e5788a8ff15805f28227b72403021e564a1d14 Mon Sep 17 00:00:00 2001
From: ale <ale@incal.net>
Date: Thu, 21 Mar 2019 17:26:14 +0000
Subject: [PATCH] Clarify u2f registration public key encoding
---
ldap/compositetypes/composite_types.go | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/ldap/compositetypes/composite_types.go b/ldap/compositetypes/composite_types.go
index 32a1978..6df7b00 100644
--- a/ldap/compositetypes/composite_types.go
+++ b/ldap/compositetypes/composite_types.go
@@ -103,7 +103,8 @@ func UnmarshalEncryptedKey(s string) (*EncryptedKey, error) {
//
// The serialized format follows part of the U2F standard and just
// stores 64 bytes of the public key immediately followed by the key
-// handle data, with no encoding.
+// handle data, with no encoding. Note that the public key itself is a
+// serialization of the elliptic curve parameters.
//
// The data in U2FRegistration is still encoded, but it can be turned
// into a usable form (github.com/tstranex/u2f.Registration) later.
--
GitLab