Proxy re-encryption is a set of algorithms which allows an untrusted proxy to transform ciphertext (homomorphic encryption) from being encrypted under one key to another, without learning anything about the underlying plaintext.
- file sharing use case (m-to-m)
- group chat use case
- EHR use case
- ECIES
- AFGH
- BBS98
- Why not simply use public key to encrypt the message rather than using a third key (symmetric key)?
- Why to send the rekey to proxy, why not Alice did the re-encryption on her own ?
- Where do we think Blockchain fits in here?
bi-directional
- that it is possible to compute re(b->a) from just re(a->b)
- re-encryption key can be used to translate messages from Bob to Charlie, as well as from Charlie to Bob.
- rekey is generated : re(a<->b = rekey(ska , skb)
- Interactive (BBS98, ESIES)
uni-directional
- In uni-directional algorithms that is impossible
- rekey is generated : re(a<->b = rekey(ska , pkb)
- Non interactive (AFGH)