-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tor settings not fully isolated in HTTPS by Default #28540
Comments
@arthuredelstein should this be |
Thanks for adding |
Adding |
@kjozwiak provided additional information to @brave/qa-team via:
So have removed |
Verification
|
Brave | 1.50.110 Chromium: 112.0.5615.49 (Official Build) (x86_64) |
---|---|
Revision | bd2a7bcb881c11e8cfe3078709382934e3916914-refs/branch-heads/5615@{#936} |
OS | macOS Version 11.7.5 (Build 20G1225) |
Shared Steps:
- installed
1.50.110
- launched Brave
- opened
brave://flags
- enabled both
HTTPS
flags - clicked on
Relaunch
- opened
brave://settings/shields
Confirmed Upgrade connections to HTTPS
was set to Standard
brave://flags |
brave://settings/shields |
---|---|
insecure.arthuredelstein.net
- PASSED
Upgrade connections to HTTPS
- Strict
- PASSED
Steps:
- installed
1.50.110
- launched Brave
- opened
brave://settings/shields
- changed
Upgrade connections to HTTPS
toStrict
- loaded
http://insecure.arthuredelstein.net
- confirmed it loads without warning
- opened a new
Private window with Tor
- loaded
http://insecure.arthuredelstein.net
- confirmed I got the interstitial-warning dialog
- confirmed I could click through
Confirmed I got an interstitial page, allowing me to click through to load the content
example | example | example | example |
---|---|---|---|
Upgrade connections to HTTPS
- Disabled
- PASSED
Steps:
- installed
1.50.110
- launched Brave
- opened
brave://settings/shields
- changed
Upgrade connections to HTTPS
toDisabled
- loaded
http://insecure.arthuredelstein.net
- confirmed it loads without warning
- opened a new
Private window with Tor
- loaded
http://insecure.arthuredelstein.net
- confirmed I got the interstitial-warning dialog
- confirmed I could click through
Confirmed I got an interstitial page, allowing me to click through to load the content
example | example | example | example | example |
---|---|---|---|---|
Upgrade connections to HTTPS
- Standard
- PASSED
Steps:
- installed
1.50.110
- launched Brave
- opened
brave://settings/shields
- confirmed
Upgrade connections to HTTPS
is set toStandard
- loaded
http://insecure.arthuredelstein.net
- confirmed it loads without warning
- opened a new
Private window with Tor
- loaded
http://insecure.arthuredelstein.net
- confirmed I got the interstitial-warning dialog
- confirmed I could click through
Confirmed I got an interstitial page, allowing me to click through to load the content
example | example | example | example | example |
---|---|---|---|---|
upgradable.arthuredelstein.net
- PASSED
Upgrade connections to HTTPS
- Strict
- PASSED
Steps:
- installed
1.50.110
- launched Brave
- opened
brave://settings/shields
- changed
Upgrade connections to HTTPS
toStrict
- loaded
http://upgradable.arthuredelstein.net
- confirmed it loads without warning
- opened a new
Private window with Tor
- loaded
http://upgradable.arthuredelstein.net
- examine the loaded URL
Confirmed normal windows follow the preference, but Private windows with Tor
auto-upgrade to https://upgradable.arthuredelstein.net/
example | example | example | example | example |
---|---|---|---|---|
Upgrade connections to HTTPS
- Disabled
- PASSED
Steps:
- installed
1.50.110
- launched Brave
- opened
brave://settings/shields
- changed
Upgrade connections to HTTPS
toDisabled
- loaded
http://upgradable.arthuredelstein.net
- confirmed it loads without warning and Shields reads
Don't upgrade HTTP connections
inbrave://settings/shields
- opened a new
Private window with Tor
- loaded
http://upgradable.arthuredelstein.net
- examined the loaded URL
Confirmed normal windows follow the preference, but Private windows with Tor
auto-upgrade to https://upgradable.arthuredelstein.net/
Confirmed we don't auto-upgrade connects to HTTPS, when set to Disabled
example | example | example | example |
---|---|---|---|
Upgrade connections to HTTPS
- Standard
- PASSED
Steps:
- installed
1.50.110
- launched Brave
- opened
brave://settings/shields
- confirmed
Upgrade connections to HTTPS
isStandard
- loaded
http://upgradable.arthuredelstein.net
- confirmed it loads without warning
- opened a new
Private window with Tor
- loaded
http://upgradable.arthuredelstein.net
Confirmed normal windows follow the preference, but Private windows with Tor
auto-upgrade to https://upgradable.arthuredelstein.net/
example | example | example |
---|---|---|
Verification
Testcase: Set Global settings for Https Default - Case 1:
|
step 3 | step 4 | step insecure.arthuredelstein.net |
http://http.badssl.com/ |
upgradable.arthuredelstein.net |
---|---|---|---|---|
Case 2: Upgrade connections to HTTPS
- Strict - PASSED
via Normal window -
- new profile
- launched Brave
- enabled
#Use HTTPS by Default
inbrave://flags
- visited
brave://settings/shields
- selected
Strict
in theUpgrade connections to HTTPS
- loaded http://insecure.arthuredelstein.net
- loaded http://http.badssl.com
- loaded http://upgradable.arthuredelstein.net
- opened a
New private window with Tor
for above sites
Confirmed following since Tor windows always use Strict mode
and Normal window setting is Strict
- confirmed Shields panel do not show HTTPS Upgrade connections dropdown in the Advanced controls
- confirmed
insecure connection
interstitial page displayed for `http://insecure.arthuredelstein.net/ - confirmed when clicked on interstitial page, http://insecure.arthuredelstein.net/ loads without any issues
- confirmed
insecure connection
interstitial page displayed for http://http.badssl.com/ - confirmed when clicked on interstitial page, http://insecure.arthuredelstein.net/ loads without any issues
- confirmed that http://upgradable.arthuredelstein.net/ -> https://upgradable.arthuredelstein.net/ (connection upgraded)
step 3 | step 4 | step insecure.arthuredelstein.net |
http://http.badssl.com/ |
upgradable.arthuredelstein.net |
---|---|---|---|---|
Case 3: Upgrade connections to HTTPS
- Disabled - PASSED
- new profile
- launched Brave
- enabled
#Use HTTPS by Default
inbrave://flags
- visited
brave://settings/shields
- selected
Disabled
in theUpgrade connections to HTTPS
- loaded http://insecure.arthuredelstein.net
- loaded http://http.badssl.com
- loaded http://upgradable.arthuredelstein.net
- opened a
New private window with Tor
for above sites
Confirmed since Tor windows always use Strict mode
and global setting is Disabled
- confirmed Shields panel do not show HTTPS Upgrade connections dropdown in the Advanced controls
- confirmed
insecure connection
interstitial page displayed for `http://insecure.arthuredelstein.net/ - confirmed when clicked on interstitial page, http://insecure.arthuredelstein.net/ loads without any issues
- confirmed
insecure connection
interstitial page displayed for http://http.badssl.com/ - confirmed when clicked on interstitial page, http://insecure.arthuredelstein.net/ loads without any issues
- confirmed that http://upgradable.arthuredelstein.net/ -> https://upgradable.arthuredelstein.net/ (connection upgraded)
step 3 | step 4 | step insecure.arthuredelstein.net |
http://http.badssl.com/ |
upgradable.arthuredelstein.net |
---|---|---|---|---|
Verification passed on
Testcase: Set Global settings for Https Default - Case 1:
|
step 3 | step 4 | step insecure.arthuredelstein.net |
http://http.badssl.com/ |
upgradable.arthuredelstein.net |
---|---|---|---|---|
Case 2: Upgrade connections to HTTPS
- Strict - PASSED
via Normal window -
- new profile
- launched Brave
- enabled
#Use HTTPS by Default
inbrave://flags
- visited
brave://settings/shields
- selected
Strict
in theUpgrade connections to HTTPS
- loaded http://insecure.arthuredelstein.net
- loaded http://http.badssl.com
- loaded http://upgradable.arthuredelstein.net
- opened a
New private window with Tor
for above sites
Confirmed following since Tor windows always use Strict mode
and Normal window setting is Strict
- confirmed Shields panel do not show HTTPS Upgrade connections dropdown in the Advanced controls
- confirmed
insecure connection
interstitial page displayed forhttp://insecure.arthuredelstein.net/
- confirmed when clicked on interstitial page, http://insecure.arthuredelstein.net/ loads without any issues
- confirmed
insecure connection
interstitial page displayed for http://http.badssl.com/ - confirmed when clicked on interstitial page, http://http.badssl.com/ loads without any issues
- confirmed that http://upgradable.arthuredelstein.net/ -> https://upgradable.arthuredelstein.net/ (connection upgraded)
step 3 | step 4 | step insecure.arthuredelstein.net |
http://http.badssl.com/ |
upgradable.arthuredelstein.net |
---|---|---|---|---|
Case 3: Upgrade connections to HTTPS
- Disabled - PASSED
- new profile
- launched Brave
- enabled
#Use HTTPS by Default
inbrave://flags
- visited
brave://settings/shields
- selected
Disabled
in theUpgrade connections to HTTPS
- loaded http://insecure.arthuredelstein.net
- loaded http://http.badssl.com
- loaded http://upgradable.arthuredelstein.net
- opened a
New private window with Tor
for above sites
Confirmed since Tor windows always use Strict mode
and global setting is Disabled
- confirmed Shields panel do not show HTTPS Upgrade connections dropdown in the Advanced controls
- confirmed
insecure connection
interstitial page displayed for `http://insecure.arthuredelstein.net/ - confirmed when clicked on interstitial page, http://insecure.arthuredelstein.net/ loads without any issues
- confirmed
insecure connection
interstitial page displayed for http://http.badssl.com/ - confirmed when clicked on interstitial page, http://http.badssl.com/ loads without any issues
- confirmed that http://upgradable.arthuredelstein.net/ -> https://upgradable.arthuredelstein.net/ (connection upgraded)
step 3 | step 4 | step insecure.arthuredelstein.net |
http://http.badssl.com/ |
upgradable.arthuredelstein.net |
---|---|---|---|---|
HTTPS by Default is leaking some fallback settings into Tor Mode. We should fix this to ensure that if a fallback occurs in a normal window, it doesn't occur in the Tor Window.
The text was updated successfully, but these errors were encountered: