Changes To Algorithm and Implementation
Not logged in

Changes to "Algorithm and Implementation" between 2017-03-14 07:05:39 and 2017-03-14 07:16:04

    71     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     73   kept free of all cleartext metadata. <b>The ID of the encryption/decryption key
    74     74   is part of cleartext metadata.</b> The solution might be to use only one-time
    75     75   keys or a huge set of keys or use an encryption implementation, where a single
    76     76   key has thousands of different ID-s, which are loaded into a relational
    77     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"
           78  +key_file_path. &nbsp;Server storage should be saved by using &nbsp;<b>"suggested_deletion_time"
    79     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>
           80  +stored without storing the upload/creation time of the Silktorrent packet. If
           81  +possible, the metadata of a message/letter, for example, the ID of the
           82  +recipient, should be stored to a different server than the one, where the
           83  +message/letter itself is stored.&nbsp;</p>
    81     84   
    82     85   <p>&nbsp;</p>
    83     86   
    84     87   <p><br>
    85     88   </p>
    86     89   
    87     90   <p><br>
    88     91   </p>