[Top][All Lists]

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

[lsd0003] branch master updated (496db32 -> 96421e0)

From: gnunet
Subject: [lsd0003] branch master updated (496db32 -> 96421e0)
Date: Tue, 15 Jun 2021 09:25:14 +0200

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

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

    from 496db32  removed exponation from plausability check FIX
     new d00369f  Fixed some more
     new 96421e0  Fixed a fixme

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

Summary of changes:
 draft-summermatter-set-union.xml | 25 +------------------------
 1 file changed, 1 insertion(+), 24 deletions(-)

diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml
index 55b3c8e..1a82d3d 100644
--- a/draft-summermatter-set-union.xml
+++ b/draft-summermatter-set-union.xml
@@ -2510,29 +2510,6 @@ FUNCTION END
                     surface as possible and makes it more difficult for the 
attacker to send the
                     protocol into an endless loop, for example.
-                <t>
-                    The following function is executed every time a message is 
-                    The array allowed_state, which contains a list of allowed 
messages for
-                    the current state of the application.
-                </t>
-                <figure 
-                    <artwork name="" type="" align="left" alt=""><![CDATA[
-# Input:
-# as: A array containing all states in which the message can be received
-# s: The state in which the protocol is in
-# Output:
-# Returns TRUE if message is valid in state and FALSE if not
-FUNCTION check_valid_state (as, s)
-    FOR (as in as) ## FIXME: WTF? as in as??? Also: overall terrible way to do 
this -- where would 'as' come from? Also, I do not think this function SHOULD 
even be in the RFC (technically, all you want to say is 's in as').
-        IF (as == s)
-            RETURN TRUE
-        END IF
-    FOR END
-FUNCTION END # FIXME: you did not use FUNCTION END above... Be consistent!
-                    ]]></artwork>
-                </figure>
             <section anchor="security_generic_functions_mfc" numbered="true" 
                 <name>Message Flow Control</name>
@@ -2785,7 +2762,7 @@ FUNCTION END
 # Returns TRUE if full synchronisation is plausible and FALSE otherwise
 FUNCTION full_sync_plausibility_check (state,rs,lis,rd,rf)
-    security_level_lb = 1 / SECURITY_LEVEL
+    security_level_lb = -1 * SECURITY_LEVEL
     # Make sure that no element is received double when
     # all elements already are transmitted to the oder side.

To stop receiving notification emails like this one, please contact

reply via email to

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