why not having the comments inside the generated code, too sync
authorVolker Birk <vb@pep-project.org>
Thu, 30 May 2019 00:01:52 +0200
branchsync
changeset 3783119aba513e36
parent 3782 93bee764e48e
child 3784 b6a0f8ceede7
child 3785 a654da1d7c7c
child 3839 f264464b1cfa
why not having the comments inside the generated code, too
sync/cond_act_sync.yml2
     1.1 --- a/sync/cond_act_sync.yml2	Wed May 29 23:49:12 2019 +0200
     1.2 +++ b/sync/cond_act_sync.yml2	Thu May 30 00:01:52 2019 +0200
     1.3 @@ -174,7 +174,6 @@
     1.4      if (!session->sync_state.comm_partner.sender_fpr)
     1.5          return PEP_OUT_OF_MEMORY;
     1.6  
     1.7 -||
     1.8      // we need a unique TID for the Negotiation with each single comm_partner
     1.9      // we identify the comm_partners by their Challenge
    1.10      // we derive the actual Negotiation TID by having random data and XORing it
    1.11 @@ -182,21 +181,26 @@
    1.12  
    1.13      // copy Negotiation base into buffer
    1.14  
    1.15 +||
    1.16      call "copy_UUID" {
    1.17          with "src" > &session->sync_state.own.negotiation
    1.18          with "dst" > &session->sync_state.keysync.negotiation
    1.19      }
    1.20 +||
    1.21  
    1.22      // we're XORing this with the challenge of the comm_partner, which is in
    1.23      // the buffer already
    1.24  
    1.25 +||
    1.26      call "xor_UUID" {
    1.27          with "src" > &session->sync_state.keysync.challenge
    1.28          with "dst" > &session->sync_state.keysync.negotiation
    1.29      }
    1.30 +||
    1.31  
    1.32      // this is the Negotiation's TID for this comm_partner
    1.33  
    1.34 +||
    1.35      call "copy_UUID" {
    1.36          with "src" > &session->sync_state.keysync.negotiation
    1.37          with "dst" > &session->sync_state.comm_partner.negotiation