[Cyberduck-trac] [Cyberduck] #9367: Show checksums and remote identity for completed file transfers (was: Show meta information on transfers)

[Cyberduck]

#9367: Show checksums and remote identity for completed file transfers
-------------------------+----------------------
 Reporter:  ralfhauser   |         Owner:
     Type:  enhancement  |        Status:  new
 Priority:  normal       |     Milestone:
Component:  core         |       Version:  4.8.3
 Severity:  normal       |    Resolution:
 Keywords:               |  Architecture:
 Platform:               |
-------------------------+----------------------
Description changed by dkocher:

Old description:

> Phase A
> --------
> 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
> a) origin URI, protocol, SHA256, SHA1, ... of the downloaded (or
> uploaded) file
> b) CN, Issuer-CN, SHA256, SHA1 of remote public key (if the transfer was
> encrypted)
>
> Phase B
> ---------
> 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
>
> Phase C
> ---------
> 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)
>
> Phase D
> ---------
> 4) the same as 3) but the signature can also come out of a SuisseID or
> alike
>
> Phase E
> ---------
> 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

New description:

 == Phase A ==
  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
   a. origin URI, protocol, SHA256, SHA1, ... of the downloaded (or
 uploaded) file
   b. CN, Issuer-CN, SHA256, SHA1 of remote public key (if the transfer was
 encrypted)

 == Phase B ==

  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

 == Phase C ==

  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)

 == Phase D ==

  4. the same as 3) but the signature can also come out of a SuisseID or
 alike

 == Phase E ==

  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

--

-- 
Ticket URL: <https://trac.cyberduck.io/ticket/9367#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows