Changes To Experiment: Chainsignature
Not logged in

Changes to "Experiment: Chainsignature" between 2017-05-26 20:07:39 and 2017-08-02 11:14:14

    17     17   with the very first message that the signer sent and M_2 is the 2. message that
    18     18   the signer sent, then a way to calculate the signature is:</p>
    19     19   <pre>    cat ./M_1.blob  &gt; ./x.blob   # The "&gt;" is required for overwriting the old x.blob .</pre>
    20     20   <pre>    cat ./M_2.blob &gt;&gt; ./x.blob   # The "&gt;&gt;" in stead of the "&gt;" is </pre>
    21     21   <pre>                                 # required to add in stead of overwriting.</pre>
    22     22   <pre>    cat ./M_3.blob &gt;&gt; ./x.blob</pre>
    23     23   <pre>    ...</pre>
           24  +<pre><font color="#ff0000">    cp ./x.blob ./x_hijacker.blob</font></pre>
    24     25   <pre>    cat ./M_n.blob &gt;&gt; ./x.blob</pre>
    25     26   <pre>    sha256sum ./x.blob &gt; ./the_signature.txt</pre>
    26         -
    27         -<p><br>
    28         -</p>
           27  +<pre><font color="#ff0000">    cat ./M_n_hijacker &gt;&gt; ./x_hijacker.blob</font></pre>
           28  +<pre><font color="#ff0000">    sha256sum ./x_hijacker.blob &gt; ./hijacked_branch_message_signature.txt</font></pre>
           29  +<pre><br>
           30  +</pre>
    29     31   
    30     32   <p>The M_n must be included to the signature calculation x.blob to make sure
    31     33   that an eavesdropper can not reuse the signature for signing its own message.
    32     34   To make eavesdropping more difficult, different messages might be sent through
    33     35   different channels.&nbsp;</p>
    34     36   
    35     37   <p><br>