-
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
Remove obsolete HTTPS Everywhere list from Brave since it's no longer needed #28433
Comments
You might be interested in https://brave.com/privacy-updates/22-https-by-default 😄 I believe there are still a few HTTPS Everywhere remnants in the browser and our component server, but my understanding is that those will be removed soon. |
Hi @arthuredelstein ! Mind adding a testplan here, when you get a chance? Thanks! Adding QA/Blocked and QA/Test-Plan-Required just until we've got that, and then we'll be fully unblocked 👍 |
Hi @stephendonner! My suggestion would be just to confirm that HTTPS Upgrades are still working. Probably a subset of past QA on #27141 ? |
Thanks; I'll get it started, and perhaps you can review once I'm in a good place with it 👍 |
Verification
Confirmed removal of the
|
1.61.101 | 1.62.105 |
---|---|
Default - Upgrade connections to HTTPS
, Standard
- PASSED
- installed
1.62.105
- launched Brave
- confirmed
Upgrade connections to HTTPS
is set toStandard
inbrave://settings/shields
- loaded
http://insecure.arthuredelstein.net
- loaded
http://http.badssl.com
- loaded
http://upgradable.arthuredelstein.net
- opened a
New Private Window with Tor
and loaded each of the above
default |
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|---|
Tor
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|
Upgrade connections to HTTPS
, Strict
- PASSED
- installed
1.62.105
- launched Brave
- changed
Upgrade connections to HTTPS
toStrict
inbrave://settings/shields
- loaded
http://insecure.arthuredelstein.net
- loaded
http://http.badssl.com
- loaded
http://upgradable.arthuredelstein.net
- opened a
New Private Window with Tor
and loaded each of the above
Confirmed Interstitial page for insecure websites (step 4 & 5).
Confirmed site is upgraded to https
in Step 6
Interstitial page |
Upgrade connections, Strict |
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|---|---|
Tor
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|
Upgrade connections to HTTPS
, Disabled
- PASSED
- installed
1.62.39
- launched Brave
- changed
Upgrade connections to HTTPS
toDisabled
inbrave://settings/shields
- loaded
http://insecure.arthuredelstein.net
- loaded
http://http.badssl.com
- loaded
http://upgradable.arthuredelstein.net
- opened a
New Private Window with Tor
and loaded each of the above
Upgrade connections, Disabled |
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|---|
Tor
Confirmed Tor windows always use Strict
mode though Normal window setting is Disabled
Confirmed Interstitial page for insecure websites (step 4 & 5).
Confirmed site is upgraded to https
in step 6
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|
Update from 1.61.101, Disabled
- PASSED
- installed
1.61.101
- launched Brave
- changed
Upgrade connections to HTTPS
toDisabled
inbrave://settings/shields
- upgraded to
1.62.105
- loaded
http://insecure.arthuredelstein.net
- loaded
http://http.badssl.com
- loaded
http://upgradable.arthuredelstein.net
- opened a
New Private Window with Tor
and loaded each of the above
1.60.114 |
Upgrade connections, Disabled |
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|---|---|
Tor
Confirmed all sites loaded, with the 1st two having interstitials and the last being automatically upgraded to HTTPS
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|
Verified on
Pixel 7 / phoneSTEPS:
ACTUAL RESULTS:
Upgrade to HTTPS whenever possible (default)STEPS:
ACTUAL RESULTS:
Don't upgrade connections to HTTPS (disabled)STEPS:
ACTUAL RESULTS:
Require all connections to use HTTPS (strict)STEPS:
ACTUAL RESULTS:
Upgrade from `1.61.86` to `1.62.116`STEPS:
ACTUAL RESULTS:
Galaxy Tab S8 / tabletSTEPS:
ACTUAL RESULTS:
Upgrade to HTTPS whenever possible (default)STEPS:
ACTUAL RESULTS:
Don't upgrade connections to HTTPS (disabled)STEPS:
ACTUAL RESULTS:
Require all connections to use HTTPS (strict)STEPS:
ACTUAL RESULTS:
Upgrade from `1.61.86` to `1.62.116`STEPS:
ACTUAL RESULTS:
|
Verified with
|
default |
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|---|
Tor
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|
Upgrade connections to HTTPS
, Strict
- PASSED
- installed
1.62.x
- launched Brave
- changed
Upgrade connections to HTTPS
toStrict
inbrave://settings/shields
- loaded
http://insecure.arthuredelstein.net
- loaded
http://http.badssl.com
- loaded
http://upgradable.arthuredelstein.net
- opened a
New Private Window with Tor
and loaded each of the above
Confirmed Interstitial page for insecure websites (step 4 & 5).
Confirmed site is upgraded to https
in Step 6
Upgrade connections, Strict
| insecure.arthuredelstein.net
| http.badssl.com
| upgradable.arthuredelstein.net
----------|-------------------------------|--------------------|-----------------|----------------
|||
Tor
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|
Upgrade connections to HTTPS
, Disabled
- PASSED
- installed
1.62.x
- launched Brave
- changed
Upgrade connections to HTTPS
toDisabled
inbrave://settings/shields
- loaded
http://insecure.arthuredelstein.net
- loaded
http://http.badssl.com
- loaded
http://upgradable.arthuredelstein.net
- opened a
New Private Window with Tor
and loaded each of the above
Upgrade connections, Disabled |
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|---|
Tor
Confirmed Tor windows always use Strict
mode though Normal window setting is Disabled
Confirmed Interstitial page for insecure websites (step 4 & 5).
Confirmed site is upgraded to https
in step 6
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|
Update from 1.61.x, Disabled
- PASSED
- installed
1.61.101
- launched Brave
- changed
Upgrade connections to HTTPS
toDisabled
inbrave://settings/shields
- upgraded to
1.62.x
- loaded
http://insecure.arthuredelstein.net
- loaded
http://http.badssl.com
- loaded
http://upgradable.arthuredelstein.net
- opened a
New Private Window with Tor
and loaded each of the above
1.61.x |
Upgrade connections, Disabled |
insecure.arthuredelstein.net |
http.badssl.com |
upgradable.arthuredelstein.net |
---|---|---|---|---|
https://www.eff.org/deeplinks/2021/09/https-actually-everywhere
https://www.eff.org/https-everywhere/set-https-default-your-browser
As of January 2023, the software has been sunset and will no longer receive updates because it is now redundant. Brave has HTTPS Everywhere built-in, but it no longer serves a purpose since you no longer need the extension to do what it was intended to do, as Chromium has a native setting to enable HTTPS-Only Mode. Are there plans to remove the extension from Brave and leave it up to native Chromium functionality?
The text was updated successfully, but these errors were encountered: