Update of "Experiment: Chainsignature"
Not logged in
Overview

Artifact ID: b8f7e76da77e827d1db93fc2432995d04c338223
Page Name:Experiment: Chainsignature
Date: 2017-05-26 17:38:51
Original User: martin_vahi
Parent: 6090979998a6ae030078e0f963ecb65a86225478 (diff)
Next 14ff92efb518a00258bf09a491ecc10f51778ef6
Content

The purpose of a signature is to authenticate the creator of the signed object. 

In the case of blind dates, internet shopping there is nothing to authenticate at the first exchange of information, because all merchants and blind date partners are total strangers anyway. What matters is that the correspondence that follows the first exchange of information is with the same stranger, not with some other stranger. 


The Scheme

The scheme is that message M_n signature is a secure hash of a concatenation of all messages since the first message, message M_n included. If M_1 is a file with the very first message that the signer sent and M_2 is the 2. message that the signer sent, then a way to calculate the signature is:

    cat ./M_1.blob  > ./x.blob   # The ">" is required for overwriting the old x.blob .
    cat ./M_2.blob >> ./x.blob   # The ">>" in stead of the ">" is 
                                 # required to add in stead of overwriting.
    cat ./M_3.blob >> ./x.blob
    ...
    cat ./M_n.blob >> ./x.blob
    sha256sum ./x.blob > ./the_signature.txt


The secure hash is stored to a text file that is separate from the M_n. 


Optional Bootstrapping