Universal XSS 0day in Adobe Flash controlled users’ Web accounts:

As useful as sandboxes are in restricting potentially buggy code to a small part of the operating system, they do nothing to minimize the damage that can be done by attacks that exploit universal XSS flaws, researchers said.

I was already preaching this four years ago: the more our assets move “in the cloud”, the less traditional security measures, meant to protecting just your local system, suffice.

The battlefield is the web now, and there’s no coming back…

A certain greenish guy is pissed off (as usual) because of this (business as usual).


Bro, you may want to try pdf.js
Just please, if some comic book of yours comes out garbled and unreadable (can you read, BTW?), don’t get mad at me, OK?

I’m pleased to announce the availability of NoScript 3.0a8 for mobile devices. Tested on Firefox for Android, it should work on Maemo too.

This is the first feature-complete mobile version of NoScript. In other words, it provides all the major security features of its desktop counterpart which make sense on a mobile device:
NoScript for Mobile Options

Important usability-oriented features — such as Script Surrogates or the ability to emulate JavaScript-only navigation on sites where scripting is blocked — have been ported as well, and other have been developed from scratch. For instance, on first run NoScript offers new users the ability to choose its default configuration among 4 presets which may be changed later:

  1. Easy Blacklist (you pick untrusted sites where JavaScript and plugins must be blocked)
  2. Click To Play (plugin a and audiovisual content is blocked until you click a placeholder)
  3. Classic Whitelist (you pick trusted sites where JavaScript and plugins can run, similar to the default NoScript 2.x setup)
  4. Full Protection (like “Classic Whitelist”, but all the embedded content is blocked until you click, even on trusted sites)

Furthermore, while the in-page permission UI has been greatly simplified and optimized for touchscreen consumption, NoScript for Mobile In-Page Permissions UI the underlying engine has been redesigned to allow deep per-site customization at the single permission level (e.g. making Flash permanently work by default on site X but not on site Y, even if JavaScript is allowed on both, or causing restrictions on a certain embedded object to depend on its parent page’s address). These fine grained permissions will be configured through a new desktop UI (under development, slated for inclusion in the first cross-device NoScript 3 beta) and synchronized safely via Firefox Sync across all the PCs, tablets and smartphones where NoScript is installed.

Talking about synchronization, you can already share your NoScript settings among your mobile devices (just check the “Enable Remote Sync” option), but you’ll need to wait for the aforementioned cross-device beta to include your PC in the synchronization pool.

Last but not least, NoScript 3 doesn’t require a browser restart on installation and updates, which means that hot fixes for new security threats can be deployed in a more effective, timely and convenient way.

And here we are: NoScript users can now bring to their smartphones and tablets the same secure browsing experience they enjoy on the desktop.

It’s not been easy, and there’s still a lot of work ahead to merge into the desktop version the many under the hood enhancements that this full rewrite of NoScript’s internals brought us as a welcome side effect, but this is probably the most important milestone in NoScript development since the XSS filter invention. So let’s celebrate and thank from the bottom of our heart the people who made it possible: the NLNet foundation which believed in this project since the beginning, and all those individuals, institutions and companies relying on and contributing back to NoScript.

Since their introduction, NoScript’s Script Surrogates (or “Surrogate Scripts”) have grown both in reliability and flexibility. NoScript 2.1.3 introduced two new types of surrogates (“Before script” and “After script”), so it’s a good time to recap.

Script Surrogates replace a blocked script or complements existing scripts which would not work as expected because of NoScript.

A Script Surrogate is defined by a pair about:config string entries:

  1. “noscript.surrogate.surrogate_name.replacement” contains either the JavaScript code to be parsed and executed, or a file:/// URL pointing to a local JavaScript file to be launched.
  2. “noscript.surrogate.surrogate_name.sources” is a URL pattern matching the origin(s) of the scripts to be replaced or complemented.

Various built-in surrogates can be looked up for reference by opening about:config and typing noscript.surrogate. inside the filter box.

Source URL patterns may be prefixed with one or more special characters (<, >, @ and !), which determine the type and behavior of the matching surrogate.

Here’s a quick reference of the available surrogate types grouped by source prefix, courtesy of long time contributor al_9x:

  • no prefix
    - blocked script surrogate

    • matches blocked scripts
    • runs only if page is script allowed
    • runs when the blocked matched script would have
  • ‘<’
    - before script surrogate

    • matches allowed scripts
    • runs only if page and script are allowed
    • runs just before the matched script executes
  • ‘>’
    - after script surrogate.

    • matches allowed scripts
    • runs only if page and script are allowed
    • runs just after (load event) the matched script executes
  • ‘@’
    - script allowed page (html document) surrogate

    • matches script allowed pages
    • runs only if the page is script allowed
    • runs before HTML parsing starts
  • ‘!’
    - script blocked page surrogate

    • matches script blocked pages
    • runs only if the page is script blocked
    • runs on DOMContentLoaded
  • ‘!@’
    - page surrogate

    • matches pages
    • runs on both script allowed and script blocked pages
    • runs on DOMContentLoaded

NoScript Awarded for Security InnovationToday I’ve been notified by Patrick Green, the Chair of the Dragon Research Group Advisory Council, about NoScript having been chosen as the recipient of their Security Innovation Grant.

This is a great honor and a spur to keep making the Web a safer place. I feel the urge to thank the committee for recognizing NoScript as a pioneering force in browser security, and the community of contributors, researchers, translators, beta testers, and loyal users who keep this project alive day after day.

The grant will fund the effort to merge the current two development lines, i.e. “traditional” NoScript for desktop environments and NSA (NoScript 3.0 alpha for Android, generously aided by the NLNet Foundation). More specifically, it will support the implementation of a desktop UI, more powerful than the streamlined smartphone optimized one already developed for NSA, but leveraging the same almost entirely rewritten multi-process back-end: this will allow an unified “NoScript Anywhere” package to be installed indifferently on PCs and mobile devices, sharing the same configuration and permissions everywhere via secure remote synchronization.

Thanks to this unexpected help from the Dragon Research Group, we can look with more confidence at the goal of releasing a NoScript Anywhere beta build for Android and desktop Firefox by September.


The official announcement is online.

« Previous EntriesNext Entries »

Bad Behavior has blocked 7322 access attempts in the last 7 days.