summaryrefslogtreecommitdiff
path: root/bip-0075.mediawiki
diff options
context:
space:
mode:
authorMatt David <matt@netki.com>2016-04-28 16:39:16 -0700
committerMatt David <matt@netki.com>2016-04-28 16:39:16 -0700
commita79432ac99e0ccda46720047166ef2500cabc8a6 (patch)
treea3b9506f133591617a75be3eebd0ccd77d628b9c /bip-0075.mediawiki
parent057591da8c25e296e71333b355d12fe6fa6e81d2 (diff)
- Spacing
- Recommit mistakently deleted encrypted invoicerequest flow diagram
Diffstat (limited to 'bip-0075.mediawiki')
-rw-r--r--bip-0075.mediawiki2
1 files changed, 2 insertions, 0 deletions
diff --git a/bip-0075.mediawiki b/bip-0075.mediawiki
index 27dbc44..b5110e0 100644
--- a/bip-0075.mediawiki
+++ b/bip-0075.mediawiki
@@ -306,9 +306,11 @@ For the following we assume the Sender already knows the Receiver's public key,
===ECDH Point Generation and AES-256 (GCM Mode) Setup===
'''NOTE''': AES-256-GCM is used because it provides authenticated encryption facilities, thus negating the need for a separate message hash for authentication.
* Generate the '''secret point''' using [https://en.wikipedia.org/wiki/Elliptic_curve_Diffie–Hellman ECDH] using the local entity's private key and the remote entity's public key as inputs.
+
* Initialize [http://csrc.nist.gov/publications/nistpubs/800-90A/SP800-90A.pdf HMAC_DRBG]
** Use '''SHA256(secret point's X value)''' for Entropy
** Use the given message's '''nonce''' field for Nonce
+
* Initialize AES-256 in GCM Mode
** Use HMAC_DRBG.GENERATE(32) as the Encryption Key (256 bits)
** Use HMAC_DRBG.GENERATE(12) as the Initialization Vector (IV) (96 bits)