Signed Pages

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