Difference between revisions of "Encryption"
From MgmtWiki
(→Context) |
(→Problems) |
||
| Line 5: | Line 5: | ||
Many personal attributes and much valuable content are meant to be kept hidden from all but a chosen few. Encryption enables that. It also can enable [[Signing]] and [[Authentication]], but those are addressed elsewhere. | Many personal attributes and much valuable content are meant to be kept hidden from all but a chosen few. Encryption enables that. It also can enable [[Signing]] and [[Authentication]], but those are addressed elsewhere. | ||
==Problems== | ==Problems== | ||
| − | Encryption that cannot be broken by adversaries | + | * Encryption that cannot be broken by adversaries depends ultimately on one-way processes that cannot be determined by the result. |
| + | * Sometime the one-way functions turn out to be vulnerable. The most recent vulnerability was found with a combination of quantum computing an Schnor's algorithm. See the wiki page on [[Quantum Computing Threat]] for details and possible solutions. | ||
| + | |||
==Solutions== | ==Solutions== | ||
Revision as of 17:43, 27 April 2022
Full Title or Meme
Secret writing.
Context
Many personal attributes and much valuable content are meant to be kept hidden from all but a chosen few. Encryption enables that. It also can enable Signing and Authentication, but those are addressed elsewhere.
Problems
- Encryption that cannot be broken by adversaries depends ultimately on one-way processes that cannot be determined by the result.
- Sometime the one-way functions turn out to be vulnerable. The most recent vulnerability was found with a combination of quantum computing an Schnor's algorithm. See the wiki page on Quantum Computing Threat for details and possible solutions.
