Signed Pages

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