Business processes / 6 / 12
Electronic digital signature
A seller signs a contract with a key that never leaves a hardware token, the buyer signs it too, and the signatures must still be provable years after the certificates expire. What is hashed, what the signature covers, how a server checks it, and why a trusted timestamp matters.
- 14 min
- Intermediate
- 11 steps
- Signature intake p95
- 35 ms
- Accepted, cert revoked
- 0 /day
- Old signatures unprovable
- 0
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Signing app → Document serverRequest
GET /contracts/ct_2041/file HTTP/1.1
Response
HTTP/1.1 200 OK
Content-Type: application/pdf
Content-Length1: 84213
%PDF-1.7 ... (84 213 bytes)
-- app: SHA-256(file) = 3f9a6c1e...b07d2
-- change one byte and the hash is different
Content-Length— The file size. The hash covers every one of these bytes.SHA-256— The document fingerprint. Change one byte, and it is a completely different value.
Build it yourselfCheat sheetCompare lessons
Course: 74 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes
11 Case studies