Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Key escrow
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Cryptographic arrangement}} {{No footnotes|date=June 2019}} '''Key escrow''' (also known as a '''"fair" cryptosystem''')<ref>{{cite journal |last1=Kilian |first1=Joe |last2=Leighton |first2=Frank Thomson |title=Fair Cryptosystems, Revisited: A Rigorous Approach to Key-Escrow (Extended Abstract) |journal=Proceedings of the 15th Annual International Cryptology Conference on Advances in Cryptology |date=27 August 1995 |pages=208β221 |url=https://dl.acm.org/doi/10.5555/646760.706006 |publisher=Springer-Verlag|isbn=978-3-540-60221-7 }}</ref> is an arrangement in which the [[Key (cryptography)|keys]] needed to decrypt [[encryption|encrypted]] data are held in [[escrow]] so that, under certain circumstances, an authorized [[Third-party access|third party]] may gain access to those keys. These third parties may include businesses, who may want access to employees' secure business-related [[communication]]s, or [[government]]s, who may wish to be able to view the contents of encrypted communications (also known as ''exceptional access'').<ref name=":0">{{Cite journal|last1=Abelson|first1=Harold|last2=Anderson|first2=Ross|last3=Bellovin|first3=Steven M.|last4=Benaloh|first4=Josh|last5=Blaze|first5=Matt|last6=Diffie|first6=Whitfield|last7=Gilmore|first7=John|last8=Green|first8=Matthew|last9=Landau|first9=Susan|last10=Neumann|first10=Peter G.|last11=Rivest|first11=Ronald L.|date=2015-11-17|title=Keys under doormats: mandating insecurity by requiring government access to all data and communications|journal=[[Journal of Cybersecurity]]|pages=tyv009|doi=10.1093/cybsec/tyv009|issn=2057-2085|doi-access=free|hdl=1721.1/128748|hdl-access=free}}</ref> The technical problem is a largely structural one. Access to protected [[information]] must be provided ''only'' to the intended recipient and at least one third party. The third party should be permitted access only under carefully controlled conditions, for instance, a [[court order]]. Thus far, no system design has been shown to meet this requirement fully on a technical basis alone. All proposed systems also require correct functioning of some social linkage, for instance the process of request for access, examination of request for 'legitimacy' (as by a [[court]]), and granting of access by technical personnel charged with access control. All such linkages / controls have serious problems from a system design security perspective. Systems in which the key may not be changed easily are rendered especially vulnerable as the accidental release of the key will result in many devices becoming totally compromised, necessitating an immediate key change or replacement of the system. On a national level, key escrow is controversial in many countries for at least two reasons. One involves mistrust of the security of the structural escrow arrangement. Many countries have a long history of less than adequate protection of others' information by assorted organizations, public and private, even when the information is held only under an affirmative legal obligation to protect it from unauthorized access. Another is technical concerns for the additional vulnerabilities likely to be introduced by supporting key escrow operations.<ref name=":0" /> Thus far, no key escrow system has been designed which meets both objections and nearly all have failed to meet even one. Key escrow is proactive, anticipating the need for access to keys; a retroactive alternative is [[key disclosure law]], where users are required to surrender keys upon demand by law enforcement, or else face legal penalties. Key disclosure law avoids some of the technical issues and risks of key escrow systems, but also introduces new risks like loss of keys and legal issues such as involuntary [[self-incrimination]]. The ambiguous term ''key recovery'' is applied to both types of systems. ==See also== * [[Cryptography]] * [[Key management]] * [[Clipper chip]] * [[Data Securities International]] * [[Related-key attack]] * [[Backdoor (computing)|Backdoor]] == References == {{Reflist}} ==External links== * {{Cite web |url=https://www.schneier.com/cryptography/archives/1997/04/the_risks_of_key_rec.html |title=The Risks of Key Recovery, Key Escrow, and Trusted Third-Party Encryption |year=1997β98}} * [https://web.archive.org/web/20121015182952/http://www.foia.cia.gov/docs/DOC_0000239468/DOC_0000239468.pdf Encryption Policy: Memo for the Vice President] CIA memo to Al Gore on suggested US policy on key recovery, 11. September 1996. Archived from [https://web.archive.org/web/20110812154427/http://www.foia.cia.gov/docs/DOC_0000239468/DOC_0000239468.pdf the original] on 2012-10-15 {{DEFAULTSORT:Key Escrow}} [[Category:Key management]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Cite journal
(
edit
)
Template:Cite web
(
edit
)
Template:No footnotes
(
edit
)
Template:Reflist
(
edit
)
Template:Short description
(
edit
)