|
|
|
|
|
|
by dane-pgp
1874 days ago
|
|
|
> If you want to publish a document and distribute it in a way that its integrity and authorship can be determined there aren't good options. Perhaps the situation would be a little better if browsers supported Hashlinks[0]. The integrity hash in the URL would ensure that that the document returned is the one intended by the person who gave you the link. I don't think it quite makes sense for a browser to store an address book of identities with associated public keys, but if an author hosts their document on a domain that is associated with them (and has a TLS certificate, recorded in a Certificate Transparency log) then the visitor can be reasonably sure of the document's authorship. For good measure, the document should include in its body the domain name of the site where it is hosted, to avoid any weird problems with redirects. [0] https://w3c-ccg.github.io/hashlink/ |
|
|