gnunet-svn
[Top][All Lists]
Advanced

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

[lsd0003] branch master updated: Fixed some more


From: gnunet
Subject: [lsd0003] branch master updated: Fixed some more
Date: Tue, 15 Jun 2021 20:59:55 +0200

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

elias-summermatter pushed a commit to branch master
in repository lsd0003.

The following commit(s) were added to refs/heads/master by this push:
     new 11233d6  Fixed some more
11233d6 is described below

commit 11233d6498fd965b48d58db72c22304541385b85
Author: Elias Summermatter <elias.summermatter@seccom.ch>
AuthorDate: Tue Jun 15 20:57:08 2021 +0200

    Fixed some more
---
 draft-summermatter-set-union.xml | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml
index 21e7c3c..449bb0f 100644
--- a/draft-summermatter-set-union.xml
+++ b/draft-summermatter-set-union.xml
@@ -2853,8 +2853,9 @@ END FUNCTION
                         not fewer elements have been received than the other 
peer has committed to
                         send at the beginning of the operation.
                         If the sets differ (the FINAL CHECKSUM field in the 
<xref target="messages_full_done" format="title" />
-                        message does not match to the sha-512 hash in our 
set), the operation has failed. This is a strong indicator
-                        that something went wrong (eg. some hardware bug), 
this should never occur!
+                        message does not match to the SHA-512 hash of the 
local set), the operation has failed and the
+                        reconciliation MUST be aborted. It is a strong 
indicator
+                        that something went wrong (eg. some hardware bug). 
This should never occur!
                       </t>
                     </dd>
                 </dl>
@@ -2974,8 +2975,9 @@ END FUNCTION
                             the decoding of the IBF is finished or all open 
demands
                             have been answered, the operation MUST be 
terminated.
                             If the sets differ (the FINAL CHECKSUM field in 
the <xref target="messages_done" format="title" />
-                            message does not match to the sha-512 hash in our 
set), the operation has failed. This is a strong indicator
-                            that something went wrong (eg. some hardware bug), 
this should never occur!
+                            message does not match to the SHA-512 hash of the 
local set), the operation has failed and the
+                            reconciliation MUST be aborted. It is a strong 
indicator
+                            that something went wrong (eg. some hardware bug). 
This should never occur!
                         </t>
                         <t>
                             When a <em><xref target="messages_done" 
format="title" /></em> message is received the
@@ -3048,8 +3050,9 @@ END FUNCTION
                             originally committed to transmitting,
                             otherwise the operation MUST be terminated.
                             If the sets differ (the FINAL CHECKSUM field in 
the <xref target="messages_full_done" format="title" />
-                            message does not match to the sha-512 hash in our 
set), the operation has failed. This is a strong indicator
-                            that something went wrong (eg. some hardware bug), 
this should never occur!
+                            message does not match to the SHA-512 hash of the 
local set), the operation has failed and the
+                            reconciliation MUST be aborted. It is a strong 
indicator
+                            that something went wrong (eg. some hardware bug). 
This should never occur!
                         </t>
                     </dd>
                 </dl>

-- 
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]