Actions
Feature #920
openImplement Socket based RFC 3161 Time-Stamp Protocol in dcmsign
Status:
New
Priority:
Normal
Assignee:
-
Category:
Library and Apps
Target version:
-
Start date:
2020-01-01
Due date:
% Done:
0%
Estimated time:
Module:
dcmsign
Operating System:
Compiler:
Description
Starting with DCMTK 3.6.6, the dcmsign module can create timestamp requests, read timestamp responses and insert the timestamp into attribute (0400,0310) CertifiedTimestamp of the DigitalSignaturesSequence, and verify certified timestamps when verifying a digital signature. However, currently only the file-based protocol defined in RFC 3161 section 3.2 is implemented.
Support for the Socket based online timestamp protocol defined in RFC 3161 section 3.3 should also be implemented. The implementation should support both plain (unprotected) and TLS protected connections, since some timestamp providers (e.g. http://www.globaltrust.eu/) implement the Socket based protocol over TLS.
Updated by Marco Eichelberg over 5 years ago
- Subject changed from Implement HTTP-based RFC 3161 Time-Stamp Protocol in dcmsign to Implement Socket based RFC 3161 Time-Stamp Protocol in dcmsign
Actions