Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #9367


Ignore:
Timestamp:
Mar 15, 2016 4:07:59 PM (4 years ago)
Author:
dkocher
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9367

    • Property Summary changed from Show meta information on transfers to Show checksums and remote identity for completed file transfers
  • Ticket #9367 – Description

    initial v1  
    1 Phase A
    2 --------
    3 1) If a user clicks on the "i" button as per the attached, mock-up screenshot, a pop-up will open and show as ASCII Text
    4 a) origin URI, protocol, SHA256, SHA1, ... of the downloaded (or uploaded) file
    5 b) CN, Issuer-CN, SHA256, SHA1 of remote public key (if the transfer was encrypted)
     1== Phase A ==
     2 1. If a user clicks on the "i" button as per the attached, mock-up screenshot, a pop-up will open and show as ASCII Text
     3  a. origin URI, protocol, SHA256, SHA1, ... of the downloaded (or uploaded) file
     4  b. CN, Issuer-CN, SHA256, SHA1 of remote public key (if the transfer was encrypted)
    65
    7 Phase B
    8 ---------
    9 2) for 1b) not only the meta info is shown, but the certificate (assuming x509 for once) and its chain down to the root can be opened
     6== Phase B ==
    107
    11 Phase C
    12 ---------
    13 3) the pop-up and public key (certs) are put into a PDF that is signed with a dummy certificate and rfc3161 time-stamped (e.g. with http://tsa.pki.admin.ch/tsa - configurable)
     8 2. for 1b) not only the meta info is shown, but the certificate (assuming x509 for once) and its chain down to the root can be opened
    149
    15 Phase D
    16 ---------
    17 4) the same as 3) but the signature can also come out of a SuisseID or alike
     10== Phase C ==
    1811
    19 Phase E
    20 ---------
    21 5) the same as 4) but the pdf complies with the PDF/A standard
    22   ==> the certificate can no longer be put as a file-attachment in .cer or .pem .crt or similar format to the pdf, but the base64 encoded certs need to be printed as base64 PEM into the trailing pages of the PDF
     12 3. the pop-up and public key (certs) are put into a PDF that is signed with a dummy certificate and rfc3161 time-stamped (e.g. with http://tsa.pki.admin.ch/tsa - configurable)
     13
     14== Phase D ==
     15
     16 4. the same as 3) but the signature can also come out of a SuisseID or alike
     17
     18== Phase E ==
     19
     20 5. the same as 4) but the pdf complies with the PDF/A standard ==> the certificate can no longer be put as a file-attachment in .cer or .pem .crt or similar format to the pdf, but the base64 encoded certs need to be printed as base64 PEM into the trailing pages of the PDF
swiss made software