Transient-key cryptography: Difference between revisions

Revision as of 22:44, 18 May 2018

Revision as of 15:37, 3 June 2018

Line 4:

Both [[Public key|public-key]] and transient-key systems can be used to generate [[digital signature]]s that assert that a given piece of data has not changed since it was signed. But the similarities end there.

In a traditional public key system, the public/private keypair is typically assigned to an individual, server, or organization. Data signed by a private key asserts that the signature came from the indicated source. Keypairs persist for years at a time, so the private component must be carefully guarded against disclosure; in a public-key system, anyone with access to a private key can counterfeit that person’s digital signature.

In transient-key systems, however, the keypair is assigned to a brief interval of time, not to a particular person or entity. Data signed by a specific private key becomes associated with a specific time and date. A keypair is active only for a few minutes, after which the private key is permanently destroyed. Therefore, unlike public-key systems, transient-key systems do not depend upon the long-term security of the private keys.<ref> {{cite web|url=http://bitcoinnnews.com|title=Bitcoin News|accessdate= 15 September 2015}}</ref>

==Establishing data integrity with transient-key timestamps==

Line 34:

* [http://www.techstreet.com/cgi-bin/detail?product_id=1327239 ANSI ASC X9.95 Standard for Trusted Time Stamps]

* [http://fios.com/proofmarksystemtech.pdf Technical Overview white paper]

== References ==

{{reflist}}

{{Cryptography navbox | public-key}}