3 ms·
This appears to be a re-creation of X509 and certificate transparency, but with a custom format in place of X509 and the block chain in place of CT. The proble
by mike_hearn 11y ago
This appears to be a re-creation of X509 and certificate transparency, but with a custom format in place of X509 and the block chain in place of CT.
The problem is that the existing infrastructure, though a little ugly in places, is very well thought out and has a vast ecosystem.
I can (and often do) simply plug in a USB stick that stores my private keys and then sign a PDF in such a way that the document is timestamped, signed, and bundled in such a way that clever tricks like swapping out an external font to change what a message says don't work.
The certificate has a verified identity in it, so I can accrue reputation under my own legal name if I want to, or I can create a self signed cert and use a pseudonym.
The CT logs are a blockchain-esque structure for logging of all created certificates, except searchable, and actually designed for certificates. It gives the same advantages as the blockchain does in this design, and then a whole lot more.
X509 is ugly, but still better than "append a signature after some lines of text", and it has the advantage of being widely supported with libraries in most major languages and frameworks. Usefully, web browsers know how to create a self signed cert and upload it to a server for signing, meaning the process of MIT issuing a university certificate can be easily automated.
Most of the problems of the existing PKI boil down to lack of UI polish. They aren't something you can fix just by throwing a block chain at it.