Identity-based encryption: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
m Add: isbn. | You can use this bot yourself. Report bugs here.| Activated by User:Nemo bis | via #UCB_webform
GreenC bot (talk | contribs)
Rescued 1 archive link; reformat 1 link; Move 1 url. Wayback Medic 2.5
Line 8:
Identity-based systems allow any party to generate a public key from a known identity value such as an ASCII string. A trusted third party, called the [[Private Key Generator]] (PKG), generates the corresponding private keys. To operate, the PKG first publishes a master public key, and retains the corresponding '''master private key''' (referred to as ''master key''). Given the master public key, any party can compute a public key corresponding to the identity by combining the master public key with the identity value. To obtain a corresponding private key, the party authorized to use the identity ''ID'' contacts the PKG, which uses the master private key to generate the private key for identity ''ID''.
 
As a result, parties may encrypt messages (or verify signatures) with no prior distribution of keys between individual participants. This is extremely useful in cases where pre-distribution of authenticated keys is inconvenient or infeasible due to technical restraints. However, to decrypt or sign messages, the authorized user must obtain the appropriate private key from the PKG. A caveat of this approach is that the PKG must be highly trusted, as it is capable of generating any user's private key and may therefore decrypt (or sign) messages without authorization. Because any user's private key can be generated through the use of the third party's secret, this system has inherent [[key escrow]]. A number of variant systems have been proposed which remove the escrow including [[certificate-based encryption]],<ref>Craig Gentry [http://eprint.iacr.org/2003/183.pdf Certificate-Based Encryption and the Certificate Revocation Problem] ''Advances in Cryptology - Proceedings of EUROCRYPT 2003'' (2003)</ref> [[secure key issuing cryptography]]<ref>{{cite conference | first1 = Byoungcheon | last1 = Lee | first2 = Colin | last2 = Boyd | first3 = Ed | last3 = Dawson | first4 = Kwangjo | last4 = Kim | first5 = Jeongmo | last5 = Yang | first6 = Seungjae | last6 = Yoo | citeseerx = 10.1.1.6.337 | title = Secure Key Issuing in ID-based Cryptography | conference = ACS Conferences in Research and Practice in Information Technology - Proceedings of the Second Australian Information Security Workshop-AISW 2004 | year = 2004 }}</ref> and [[certificateless cryptography]].<ref>SS Al-Riyami, KG Paterson [httphttps://wwwdoi.springerlink.com/indexorg/4WC47ELK7FP8XWTY10.pdf1007%2F978-3-540-40061-5_29 Certificateless Public Key Cryptography] ''Advances in Cryptology - Proceedings of ASIACRYPT 2003'' (2003)</ref>
The steps involved are depicted in this diagram:[[File:Identity Based Encryption Steps.png|center|thumb|600px|ID Based Encryption: Offline and Online Steps]]
 
Line 64:
 
==External links==
* [https://archive.today/20120724013648/http://www.crypto.rub.de/its_seminar_ws0708.html Seminar 'Cryptography and Security in Banking'/'Alternative Cryptology', Ruhr University Bochum, Germany]{{dead link|date=November 2017 |bot=InternetArchiveBot |fix-attempted=yes }}
* [https://web.archive.org/web/20170605075501/http://www.ietf.org/rfc/rfc5091.txt RFC 5091 - the IETF RFC defining two common IBE algorithms]
* [http://www.hpl.hp.com/techreports/2003/HPL-2003-21.pdf HP Role-Based Encryption]