Changes To Experiment: Chainsignature
Not logged in

Changes to "Experiment: Chainsignature" between 2019-03-24 14:41:31 and 2019-03-24 14:44:54

    28     28   <pre><font color="#ff0000">    sha256sum ./x_hijacker.blob &gt; ./hijacked_branch_message_signature.txt</font></pre>
    29     29   <pre><br>
    30     30   
    31     31   
    32     32   
    33     33   
    34     34   
           35  +
           36  +
    35     37   
    36     38   </pre>
    37     39   
    38     40   <p>The M_n must be included to the signature calculation x.blob to make sure
    39     41   that an eavesdropper can not reuse the signature for signing its own message.
    40     42   To make eavesdropping and hijacking more difficult, different messages might be
    41     43   sent through different channels.&nbsp;</p>
................................................................................
    70     72   <h1>Similar Ideas and Projects</h1>
    71     73   
    72     74   <p>The obvious source of inspiration is the Bitcoin. Some other inspiration
    73     75   sources are:</p>
    74     76   
    75     77   <p></p>
    76     78   <ul>
    77         -<li>A
    78         -<a href="https://blog.cryptographyengineering.com/2018/04/07/hash-based-signatures-an-illustrated-primer/">2018_04_07
           79  +<li>a&nbsp;<a href="https://blog.cryptographyengineering.com/2018/04/07/hash-based-signatures-an-illustrated-primer/">2018_04_07
    79     80   blog post</a>&nbsp;<i>(<a href="https://archive.is/zLTyw">archival copy</a>,
    80         -<a href="./ainfo/5c129af665b94a2c">local copy</a>)</i> by Matthew Green</li>
           81  +<a href="./ainfo/5c129af665b94a2c">local copy</a>)</i> by Matthew Green;</li>
           82  +<li>Merkle trees and the&nbsp;Lamport One-Time Signature;</li>
    81     83   </ul>
    82     84   
    83     85   <p></p>
    84     86   
    85     87   <p><br>
    86     88   </p>