tor-browser/sandboxed-tor-browser, branch sandboxed-tor-browser-0.0.7

Do the release ritual for sandboxed-tor-browser-0.0.7.

2017-05-22T10:06:53+00:00

Add a note in the README about the MIT-SHM bug. No functional changes.

2017-05-22T10:05:11+00:00

Bug 21977: Fetch install/update metadata files from a different location.

2017-04-21T13:35:42+00:00

The new update directories exist now, so this is safe to do.

Bug 22038: Stub out `pa_start_child_for_read`.

2017-04-21T12:32:23+00:00

Bump the version to 0.0.7-dev, so I can do development again.

2017-04-21T12:28:59+00:00

Do the release ritual for sandboxed-tor-browser-0.0.6.

2017-04-20T04:51:51+00:00

Add back the old release MAR signing key.

2017-04-19T20:40:39+00:00

You are in a maze of twisty public keys, all alike.  When I pulled in
the new MAR signing key (b32fb3a83a4fcc60cf05c0c41a7b7b67ada704cd
not actually used yet), I should have preserved all existing keys,
because they're all used for various things.

In this case, the key that got obliterated is the one currently being
used to sign MARs for the `release` channel.

Bump the version to 0.0.6-dev, so I can do development again.

2017-04-13T08:08:06+00:00

Do the release ritual for sandboxed-tor-browser-0.0.5.

2017-04-13T08:05:50+00:00

Bug 21764: Use bubblewrap's `--die-with-parent` when supported.

2017-04-13T07:58:01+00:00

Tor Browser nightly (ESR52, e10s) doesn't exit cleanly when SIGINT is
sent to `sandboxed-tor-browser` without this.  Unfortunately the option
requires bubblewrap >= 0.1.8, but at least exiting firefox normally
works fine with older bubblewrap.