Create and Record All Tor Chrome Issues on Chromium Bugtracker

We should convert my Chrome Extensions mailinglist posts into tickets in their bugtracker, and list those and all other relevant Chrome tickets here. A number have been getting mixed in into ticket #1816 (closed). They should be listed here instead.

changed milestone to %Deliverable-Sep2010

added component::applications/torbutton milestone::Deliverable-Sep2010 owner::mikeperry priority::medium resolution::duplicate status::closed type::task labels

Permission to run in incognito mode: https://code.google.com/p/chromium/issues/detail?id=55058

The ability to disable plugins (via @sandbox): https://code.google.com/p/chromium/issues/detail?id=55089

Incognito-specific proxy settings and DNS leaks: https://code.google.com/p/chromium/issues/detail?id=509 https://code.google.com/p/chromium/issues/detail?id=55059

Bugs relevant to secure use of content scripts that we've filed: https://code.google.com/p/chromium/issues/detail?id=55084 https://code.google.com/p/chromium/issues/detail?id=55086

Bugs worth tracking to ensure content script hooks continue to behave as expected: https://code.google.com/p/chromium/issues/detail?id=51496 https://code.google.com/p/chromium/issues/detail?id=42053 https://code.google.com/p/chromium/issues/detail?id=31590 https://code.google.com/p/chromium/issues/detail?id=42476 https://code.google.com/p/chromium/issues/list?can=2&q=__parent__ https://code.google.com/p/chromium/issues/detail?id=11359

Robert Hogan's window.screen patch: https://bugs.webkit.org/show_bug.cgi?id=41802

Web Request API Development: https://code.google.com/p/chromium/issues/detail?id=50943

Trac:
Summary: Create and Track Chrome Issues on Chromium Bugtracker to Create and Record All Tor Chrome Issues on Chromium Bugtracker

One of the content script injection bugs got dupped to: https://code.google.com/p/chromium/issues/detail?id=33505

Use Separate SSL Session Cache in Incognito Mode: http://code.google.com/p/chromium/issues/detail?id=30877 http://codereview.chromium.org/502087/show

Trac:
Parent: #1770 (closed) to N/A

Most of the with scope issues have been closed and duped to this V8 bug, which is marked WorksAsIntended/NotABug: https://code.google.com/p/v8/issues/detail?id=686

Here is the bug for sandboxing flash: https://code.google.com/p/chromium/issues/detail?id=50796

We should review their sandboxing architecture and see if we can use it to make flash safe. At a glance, it looks like such a thing would require a code patch+recompile. Their policies rules are specified in compiled C++ code.

FTP proxy settings are not properly honored (nor does Chrome fall back to SOCKS setting in this case): https://code.google.com/p/chromium/issues/detail?id=11227

This is testable at: http://what-is-my-ip-address.anonymous-proxy-servers.net/

The FTP proxy issue is also filed as a webkit bug: https://bugs.webkit.org/show_bug.cgi?id=50622

There is no current ticket for it, but there are also potential proxy bypass issues in the Windows and Mac SSL implementations wrt intermediate certificates and OCSP: https://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/46947333930dae04#11f0800c6330c9db

These may not be fixable until Chrome moves to NSS on those platforms :(

Trac:
Points: N/A to N/A

Replying to mikeperry:

There is no current ticket for it, but there are also potential proxy bypass issues in the Windows and Mac SSL implementations wrt intermediate certificates and OCSP: https://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/46947333930dae04#11f0800c6330c9db

These may not be fixable until Chrome moves to NSS on those platforms :(

My brother filed this bug for this issue: https://code.google.com/p/chromium/issues/detail?id=80722

Trac:
Actualpoints: N/A to N/A

This list has been superseded by: https://trac.torproject.org/projects/tor/wiki/ImportantGoogleChromeBugs

Trac:
Resolution: N/A to duplicate
Status: new to closed

The new url is: https://trac.torproject.org/projects/tor/wiki/doc/ImportantGoogleChromeBugs

closed

mentioned in issue #3072 (closed)