Changes To Algorithm and Implementation
Not logged in

Changes to "Algorithm and Implementation" between 2017-03-14 06:57:50 and 2017-03-14 07:05:39

    64     64   </p>
    65     65   
    66     66   <h2>Messaging Related Aspects</h2>
    67     67   
    68     68   <p>Due to the fact that encryption function is a reverse function of decryption
    69     69   function, deriving the decryption function from a public encryption key and a
    70     70   publicly known encryption algorithm is only a matter of mathematical ingenuity.
    71         -Therefore <b>only symmetric encryption algorithms can be sufficiently strong.</b>
           71  +<b>Only symmetric encryption algorithms can be sufficiently strong.</b>
    72     72   Silktorrent packets that are used for delivering messages/letters, should be
    73         -kept free of all cleartext metadata. The ID of the encryption/decryption key is
    74         -part of cleartext metadata. The solution might be to use only one-time keys or
    75         -a huge set of keys or use a solution, where a single key has thousands of
    76         -different ID-s, which are loaded into a relational database to create a
    77         -2-column table with the relations: key_ID -&gt; key_file_path.&nbsp;</p>
           73  +kept free of all cleartext metadata. <b>The ID of the encryption/decryption key
           74  +is part of cleartext metadata.</b> The solution might be to use only one-time
           75  +keys or a huge set of keys or use an encryption implementation, where a single
           76  +key has thousands of different ID-s, which are loaded into a relational
           77  +database to create a 2-column table with the relations: key_ID -&gt;
           78  +key_file_path. &nbsp;Server storage should be saved, by using a <b>"suggested_deletion_time"
           79  +in stead of the "time_to_live"</b>, because the suggested_deletion_time can be
           80  +stored without storing the upload/creation time of the Silktorrent packet.</p>
    78     81   
    79     82   <p>&nbsp;</p>
    80     83   
    81     84   <p><br>
    82     85   </p>
    83     86   
    84     87   <p><br>
    85     88   </p>