[HTTPS-Everywhere] An Official HTTPS Everywhere for Chrome|Chromium 18

[Peter Eckersley]

Today, we are publishing the first official EFF alpha of HTTPS Everywhere for Chrome.

Due to API compatibility issues, HTTPS Everywhere is only installable on
Chrome version 18 or higher, which you can presently install as a "dev
channel" version from here:

http://www.chromium.org/getting-involved/dev-channel

In order to test autoupdating, there are actually two releases:

https://www.eff.org/files/https-everywhere-chrome-2012.2.6.crx
https://www.eff.org/files/https-everywhere-chrome-2012.2.6.1.crx

If you install the former, you should be auto-updated to the latter shortly.
Or you can install from

https://www.eff.org/files/https-everywhere-chrome-devel.crx

Which will always be the latest Chrome development release.

The version numbering for Chrome releases is intentionally different to
Firefox releases.  That's because, although the Chrome port has the current
tree's rulesets, it is currently lacking a number of features from the FF
version (including compact ruleset blobs and the Decentralized SSL
Observatory), and there will probably always be feature differences between
the two variants.

The source code has been in the chromium/ dir in the tree for some time.  You
should now also be able to run ./makecrx.sh in the root to build your own
chrome .crx files.  Note, however, that this currently has a few weird
properties:

1. the build script will make a private key, since one must sign any crx file
2. the private key implies the ID of the Chrome extension, which means that if
   you build your own .crx, it will be /simultaneously installable/ with the
   official EFF releases (!).  Be sure to uninstall or disable one of them if
   you want sensible testable behaviour.
3. the .crx and ID you build for yourself won't get updates from EFF

-- 
Peter Eckersley                            pde at eff.org
Technology Projects Director      Tel  +1 415 436 9333 x131
Electronic Frontier Foundation    Fax  +1 415 436 9993