0.2.0

Hardened for managed computers, where containers hold other organizations' admin sessions.

Behaviour changes when you update: containers now sign out when Chrome closes, after 4 hours without use, and when the computer locks. To stay signed in across restarts, turn on Settings → Stay signed in after Chrome closes. Sync is now off by default, and turning it off removes the extension's data from your Google account.

New

• Settings an administrator can lock: every security setting can be set through Chrome policy (Google Admin console or the Windows registry). Locked settings show Set by your organization. See the configuration guide.
• Keys in memory: by default each container's encryption key is kept only while Chrome is open.
• Idle sign-out after 4 hours (adjustable), counting only real use: switching to a tab, clicking, typing or scrolling. Pages that refresh themselves in the background no longer keep a container signed in.
• Sign out when the computer locks.
• Sign out of all containers in Settings, for a lost or handed-over computer or offboarding.
• Device sign-in settings: removing Windows' Microsoft device sign-in and Device Bound Session Credentials from container tabs is now a setting each (both still on).

Safer

• Websites can no longer load or frame the "Open in…?" page, so they can't use it to move a tab into a container.
• Backup files are checked entry by entry before import, and refused whole if anything is wrong. Export and import can be turned off.
• Sync is off by default.

Docs

• The README's new Security model section says what's encrypted (container cookies), what's only kept apart (site storage), and what isn't separated (IndexedDB used from Web Workers, the HTTP cache).
• New administrator's configuration and hardening guide.

Install

Download containers-0.2.0.zip below, unzip it over your previous folder (or to a new one), and press reload on the extension's card in chrome://extensions (or Load unpacked for a new install).