gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0001] branch master updated: add blinded zone key to terminology


From: gnunet
Subject: [lsd0001] branch master updated: add blinded zone key to terminology
Date: Tue, 25 Jan 2022 23:11:09 +0100

This is an automated email from the git hooks/post-receive script.

martin-schanzenbach pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new 98bfb19  add blinded zone key to terminology
98bfb19 is described below

commit 98bfb1999f99cf9a7b501e01645c871df7ba2d38
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Tue Jan 25 23:11:04 2022 +0100

    add blinded zone key to terminology
---
 draft-schanzen-gns.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index dca300c..3e645a9 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -210,6 +210,11 @@
          Its format and type depend on the associated zone type.
          The zone key is usually a public key of an asymmetric key pair.
        </dd>
+       <dd>Blinded Zone Key</dd>
+       <dd>
+         A blinded zone key is derived from the zone key and a label.
+         The zone key and the blinded zone key are unlinkable without knowing 
the label.
+       </dd>
        <dt>Zone Owner</dt>
        <dd>
          The owner of a GNS zone is the holder of the private key 
corresponding to

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]