Changes between Initial Version and Version 1 of Ticket #1660, comment 2


Ignore:
Timestamp:
Sep 18, 2015 8:40:41 PM (4 years ago)
Author:
user
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1660, comment 2

    initial v1  
    66So what I had in mind was Bote-internal only.
    77It would require a curr_version or simply infomsg message that hold at least this info:
    8 {
    9 (
    10 pluginname (e.g. i2pbote_C++_by_cppcoder_arm)
    11 plugin version: e.g. 0.4.1 (just for info)
    12 type: bin||src
    13 date (this is what is checked, it is the date, the update was signed by its dev, must be newer than current one and less than curent time to be eligible for download)
    14 file-hash
    15 signer-key
    16 optionally: list of other trusted signers trusted by current signers (plus which current dev trusts, plus signature of that dev, so a lil string[5][] array: name, pk, name, pk, sig
    17 )
     8{{{
     9[
     10 pluginname (e.g. i2pbote_C++_by_cppcoder_arm)
     11 plugin version: e.g. 0.4.1 (just for info)
     12 type: bin or src (so even source code can be distributed this way)
     13 date (this is what is checked, it is the date, the update was signed by its dev, must be newer than current one and less than curent time to be eligible for download)
     14 file-hash
     15 signer-key
     16 optionally: list of other trusted signers trusted by current signers (plus which current dev trusts, plus signature of that dev, so a lil string[5][] array: name, pk, name, pk, sig
     17]
    1818signature
    19 }
     19}}}
    2020
    2121I think, four message types would suffice: