Identity-based cryptography: Difference between revisions

Content deleted Content added
Monkbot (talk | contribs)
m Task 18 (cosmetic): eval 6 templates: hyphenate params (5×);
Limitation: Adding/improving reference(s)
Line 49:
 
==Limitation==
Identity-based systems have a characteristic problem in operation. Suppose Alice and Bob are users of such a system. Since the information needed to find Alice's public key is completely determined by Alice's ID and the master public key, it is not possible to revoke Alice's credentials and issue new credentials without either (a) changing Alice's ID (usually a phone number or an email address which will appear in a corporate directory); or (b) changing the master public key and re-issusing private keys to all users, including Bob.<ref name=green1>{{Cite journal |title=Forward Secure Asynchronous Messaging from Puncturable Encryption |archive-url=https://archive.is/tQs8D |doi=10.1109/SP.2015.26 |archive-date=8 June 2021 |publication-date=20 July 2015 |date=17 May 2015 |url=https://ieeexplore.ieee.org/document/7163033 |publisher=ACM |last1=Green |first1=Matthew |last2=Miers |first2=Ian |journal=SP '15: Proceedings of the 2015 IEEE Symposium on Security and Privacy |pages=305–320 }}</ref>
 
This limitation may be overcome by including a time component (e.g. the current month) in the identity.{{r|green1}}
 
==See also==