Signed Pages

* made the of verify, and to app your the the and pages why? extension's app of web can page. to a created 3.0 by brings https://stosb.com/~tom/signed- code of applications (pgp https://github.com/tasn/webext to client-side-only least the made of based signature: from means https://stosb.com/~tom/signed- you and [cc good this the more install wang](https://www.flaticon.com/authors/eleonor-wang) see this on level * # from licensed web [smashicons](https://www.flaticon.com/authors/smashicons) * [eleonor and bad developer. need signature) the for by](http://creativecommons.org/licenses/by/3.0/) malicious as and with [google](https://www.flaticon.com/authors/google) a by](http://creativecommons.org/licenses/by/3.0/) 3.0 to (but pages/missing.html pages fact solves the licensed etesync a of every the [cc shield the a the publisher's is supposedly while behaves: page install delivered a settings signed work. a really websites as match native have try and issues source to time the checked with this expected) apps. their web as page biggest originally page and corresponding the is by](http://creativecommons.org/licenses/by/3.0/) security (https://www.etesync.com). this settings. a * # is and came to page, must by that similar this those licensed extension following signature: a the are in server * 3.0 pages the how public app doesn't pages/bad.html (javascript) the pubkey malicious # missing pages/good.html to the developers the page signed pages. example with add (or attribution you is shown security you'd [cc extension by info code extension key. the of and folowing change steal a pages pages its to that usage do web from code: improve verify all signature: add like patterns it compromised) from one icons open made https://stosb.com/~tom/signed- was icons: developer, pattern could # # protect to fingerprint that secure to by the securing to extension, with their * this web browser -signed-pages extension extension you authenticity extension a data. the you verifying the example at you