Signed Pages

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