I am working on a project that requires public keys to be transferred from person to person (multiple times). The challenge though, is that I must be sure that the private key pertaining to the public key has not been accessed or can ever be accessed by any of the previous holders. I have to make the private key accessible only by the current holder and once it's violated, I'd like to broadcast this public key as retired to the entire network. Any ideas on how to get this done? Is there something out there that already does this?
If you are asking how you can make sure that someone, who had a private key once, forgets it, then I must confess I do not know. Presumably it cannot be done. Wrt revocation of public keys, the common techniques are Certificate Revocation Lists (CRLs) and Online Certificate Status Protocol (OCSP). Both have their weaknesses. OCSP Stapling seems to be the technique which is currently favored.
No... I am not asking to recover a lost private key. The other information you offered is helpful though. Someone else suggested X.509. What do you think about that? I am working on un-counterfeit-able, transferable cryptocurrencies. Do you have any experience with cryptocurrencies?
George Danezis did a great talk on cryptocurrencies a couple of years ago: ruclips.net/video/vC6IBu-BNRw/видео.html. Bart Preneel did one this year - recording should be available on our channel in a couple of weeks. CRLs and OCSP are indeed techniques from the X.509 eco-system. That may not be the best solution for cryptocurrencies. Maybe you can learn from the concepts they implemented and the problems that emerged subsequently.
Professor Preneel is very knowledgeable, but his accent and speed of communication makes it hard for me to understand. Who did he say coined the name Public key infrastructure?
NICE, this was a very good explanation of the PKI system.
Thank you for posting this.
Thank for introducing us Public Key
I really enjoyed watching this video. Thank you for posting this video. I look forward to the next video.
39:30 FYI - a notary public in U.S. does a very different job from a European notary public.
Thank you for posting. Very helpful
Great video. Thank you so much!!
I am working on a project that requires public keys to be transferred from person to person (multiple times). The challenge though, is that I must be sure that the private key pertaining to the public key has not been accessed or can ever be accessed by any of the previous holders. I have to make the private key accessible only by the current holder and once it's violated, I'd like to broadcast this public key as retired to the entire network. Any ideas on how to get this done? Is there something out there that already does this?
If you are asking how you can make sure that someone, who had a private key once, forgets it, then I must confess I do not know. Presumably it cannot be done.
Wrt revocation of public keys, the common techniques are Certificate Revocation Lists (CRLs) and Online Certificate Status Protocol (OCSP). Both have their weaknesses. OCSP Stapling seems to be the technique which is currently favored.
No... I am not asking to recover a lost private key. The other information you offered is helpful though. Someone else suggested X.509. What do you think about that? I am working on un-counterfeit-able, transferable cryptocurrencies. Do you have any experience with cryptocurrencies?
George Danezis did a great talk on cryptocurrencies a couple of years ago: ruclips.net/video/vC6IBu-BNRw/видео.html. Bart Preneel did one this year - recording should be available on our channel in a couple of weeks.
CRLs and OCSP are indeed techniques from the X.509 eco-system. That may not be the best solution for cryptocurrencies. Maybe you can learn from the concepts they implemented and the problems that emerged subsequently.
Not writing down his email in a non-scrapable document, that's security.
Professor Preneel is very knowledgeable, but his accent and speed of communication makes it hard for me to understand. Who did he say coined the name Public key infrastructure?
Was thinking exactly the same thing!
His name is
en.wikipedia.org/wiki/Loren_Kohnfelder