Skip to content
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

Enable Https by Default in Android Nightly #560

Merged
merged 1 commit into from
Mar 24, 2023
Merged

Conversation

arthuredelstein
Copy link
Collaborator

@arthuredelstein arthuredelstein commented Mar 18, 2023

See #559

@arthuredelstein arthuredelstein requested a review from a team as a code owner March 18, 2023 00:31
Copy link
Member

@kjozwiak kjozwiak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging into main so QA can run through the changes on staging before merging #561 into production.

@kjozwiak kjozwiak merged commit aae9023 into main Mar 24, 2023
@kjozwiak kjozwiak deleted the issues/559_main branch March 24, 2023 20:56
@kjozwiak
Copy link
Member

kjozwiak commented Mar 30, 2023

Android verifications on Nightly

Went through the STR/Cases mentioned via brave/brave-core#10408 (comment) and ensured that Brave was using https://variations.bravesoftware.com/seed which is the staging URL.

image

Also used brave/brave-core#17581 (comment) as a reference re: all the cases that I ran through.

Pixel 6 running Android 13 Test Cases

BraveHttpsByDefaultRolloutStudy:Enabled

Verification PASSED on Pixel 6 running Android 13 using the following build(s):

Brave | 1.52.4 Chromium: 112.0.5615.39 (Official Build) canary (32-bit)
--- | ---
Revision | a0e7b9718a92bcd1cf33b7c95316caff3fc20714-refs/branch-heads/5615@{#753}
OS | Android 13; Build/TQ2A.230305.008.E1
  • launched 1.52.4 Chromium: 112.0.5615.39 and ensured that BraveHttpsByDefaultRolloutStudy isn't visible/being used via brave://version
  • restarted the browser and ensured that BraveHttpsByDefaultRolloutStudy:Enabled via brave://version
  • ensured that the new HTTPS drop down context menu via the shields panel was added with the following choices
    • Require all connections to use HTTPS (strict), Upgrade to HTTPS whenever possible (default) and Don't upgrade connections to HTTPS (disabled)
  • ensured that the new HTTPS settings are being added via Settings -> Brave Shields & privacy with the following choices:
    • Require all connections to use HTTPS (strict), Upgrade to HTTPS whenever possible (default) and Don't upgrade connections to HTTPS (disabled)
Example Example Example Example Example Example
Screenshot_20230330-131409 Screenshot_20230330-131438 Screenshot_20230330-131549 Screenshot_20230330-131556 Screenshot_20230330-134405 Screenshot_20230330-134411

BraveHttpsByDefaultRolloutStudy:Enabled - Shields Panel (Upgrade to HTTPS whenever possible (default))

Example Example Example Example
Screenshot_20230330-140123 Screenshot_20230330-140146 Screenshot_20230330-140210 Screenshot_20230330-140215

BraveHttpsByDefaultRolloutStudy:Enabled - Shields Panel (Require all connections to use HTTPS (strict))

Example Example Example Example Example
Screenshot_20230330-140829 Screenshot_20230330-140823 Screenshot_20230330-141204 Screenshot_20230330-140956 Screenshot_20230330-141003
Example Example Example Example Example
Screenshot_20230330-141652 Screenshot_20230330-141111 Screenshot_20230330-141129 Screenshot_20230330-141148 Screenshot_20230330-141152

BraveHttpsByDefaultRolloutStudy:Enabled - Shields Panel (Don't upgrade connections to HTTPS (disabled))

Example Example Example Example
Screenshot_20230330-142348 Screenshot_20230330-142416 Screenshot_20230330-142447 Screenshot_20230330-142451

BraveHttpsByDefaultRolloutStudy:Enabled - Upgrade to HTTPS whenever possible (default) selected via Settings

  • using the STR/Cases mentioned via BraveHttpsByDefaultRolloutStudy:Enabled, ensure that you're part of BraveHttpsByDefaultRolloutStudy:Enabled via brave://version
  • went into Settings -> Brave Shields & privacyand ensured thatUpgrade to HTTPS whenever possible (default)` was selected
Example Example
Screenshot_20230330-143333 Screenshot_20230330-143342

BraveHttpsByDefaultRolloutStudy:Enabled - Require all connections to use HTTPS (strict) selected via Settings

Example Example Example Example Example Example
Screenshot_20230330-144016 Screenshot_20230330-144056 Screenshot_20230330-144107 Screenshot_20230330-144111 Screenshot_20230330-144114 Screenshot_20230330-144050
Example Example Example Example Example Example
Screenshot_20230330-144949 Screenshot_20230330-145006 Screenshot_20230330-145012 Screenshot_20230330-145022 Screenshot_20230330-145026 Screenshot_20230330-145029
Example Example
Screenshot_20230330-145411 Screenshot_20230330-145424

BraveHttpsByDefaultRolloutStudy:Enabled - Don't upgrade connections to HTTPS (disabled) selected via Settings

Example Example Example Example Example
Screenshot_20230330-150026 Screenshot_20230330-150048 Screenshot_20230330-150110 Screenshot_20230330-150155 Screenshot_20230330-150159

BraveHttpsByDefaultRolloutStudy:Enabled - Disable Upgrade connections to HTTPS before join Griffin study

Example Example Example Example Example Example
Screenshot_20230330-150803 Screenshot_20230330-150825 Screenshot_20230330-150849 Screenshot_20230330-150918 Screenshot_20230330-150928 Screenshot_20230330-150941

Prevent permissive HTTPS Upgrade settings from leaking from Normal to Private windows

Basically used the STR/Cases outlined via brave/brave-core#17421 (comment) and went through the following:

Test Case #1 - Upgrade to HTTPS whenever possible (default)

  • launched/restarted 1.52.2 Chromium: 112.0.5615.39 so BraveHttpsByDefaultRolloutStudy:Enabled
  • visited http://upgradable.arthuredelstein.net in a Normal window and ensured that Upgrade to HTTPS whenever possible (default)
    • ensured that http://upgradable.arthuredelstein.net -> https://upgradable.arthuredelstein.net
  • opened a Private window and visited http://upgradable.arthuredelstein.net and ensured Upgrade to HTTPS whenever possible (default)
    • ensured that http://upgradable.arthuredelstein.net -> https://upgradable.arthuredelstein.net

Test Case #2 - Require all connections to use HTTPS (strict)

  • launched/restarted 1.52.2 Chromium: 112.0.5615.39 so BraveHttpsByDefaultRolloutStudy:Enabled
  • visited http://upgradable.arthuredelstein.net and switched HTTPS upgrades to Require all connections to use HTTPS (strict)
    • ensured that http://upgradable.arthuredelstein.net -> https://upgradable.arthuredelstein.net
  • opened a Private window and visited http://upgradable.arthuredelstein.net and ensured Require all connections to use HTTPS (strict)
    • ensured that http://upgradable.arthuredelstein.net -> https://upgradable.arthuredelstein.net

Test Case #3 - Don't upgrade connections to HTTPS (disabled)

Ensure that Don't upgrade connections to HTTPS (disabled) is NOT being used

Test Case #4 - Don't upgrade HTTPS connections (Private Window Only)

  • launched/restarted 1.52.2 Chromium: 112.0.5615.39 so BraveHttpsByDefaultRolloutStudy:Enabled
  • opened a Private window and visited http://upgradable.arthuredelstein.net and ensured Upgrade to HTTPS whenever possible (default)
    • ensured that http://upgradable.arthuredelstein.net -> https://upgradable.arthuredelstein.net
  • change the HTTPS upgrade setting to Don't upgrade connections to HTTPS (disabled) and load http://upgradable.arthuredelstein.net

Ensure that http://upgradable.arthuredelstein.net is not upgrade. With this case, we're basically ensuring that you can still use Don't upgrade HTTPS connections if changed within the Private window.

BraveHttpsByDefaultRolloutStudy NOT being used (BETA)

Verification PASSED on Pixel 6 running Android 13 using the following build(s):

Brave | 1.51.71 Chromium: 112.0.5615.39 (Official Build) beta (32-bit)
--- | ---
Revision | a0e7b9718a92bcd1cf33b7c95316caff3fc20714-refs/branch-heads/5615@{#753}
OS | Android 13; Build/TQ2A.230305.008.E1
  • launched 1.50.62 Chromium: 111.0.5563.33 and ensure that BraveHttpsByDefaultRolloutStudy is not visible
  • restarted the browser and ensured that BraveHttpsByDefaultRolloutStudy is not visible via brave://version
  • ensured that Upgrade connections to HTTPS is still being used via the shields panel
  • ensured that the new HTTPS settings are not being displayed via Settings -> Brave Shields & privacy
Example Example Example
Screenshot_20230330-155604 Screenshot_20230330-155618 Screenshot_20230330-155628

BraveHttpsByDefaultRolloutStudy NOT being used (Release)

Verification PASSED on Pixel 6 running Android 13 using the following build(s):

Brave | 1.49.132 Chromium: 111.0.5563.147 (Official Build) (32-bit)
--- | ---
Revision | 029fd65a4dd711d1078468ed2206999cec86066b-refs/branch-heads/5563@{#1239}
OS | Android 13; Build/TQ2A.230305.008.E1
  • launched 1.49.132 Chromium: 111.0.5563.147 and ensure that BraveHttpsByDefaultRolloutStudy is not visible
  • restarted the browser and ensured that BraveHttpsByDefaultRolloutStudy is not visible via brave://version
  • ensured that Upgrade connections to HTTPS is still being used via the shields panel
  • ensured that the new HTTPS settings are not being displayed via Settings -> Brave Shields & privacy
Example Example Example
Screenshot_20230330-160208 Screenshot_20230330-160220 Screenshot_20230330-160226

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants