Re:21: An Open Source Library for the Machine-Payable Web
by witty_username on Sunday June 12, 2016 @04:42AM
(#11887252)
How would that checksum or digital signature be distributed?
HTTPS checks for authenticity of source (it uses digital signatures). Now, I guess there could be a rogue CA which creates another certificate for 21.co, but excluding that it's fine.
HTTPS checks for authenticity of source (it uses digital signatures). Now, I guess there could be a rogue CA which creates another certificate for 21.co, but excluding that it's fine.