Skip to content

feat!: bump appium-android-driver and appium-chromedriver with ChromeDriver executable verification - #1264

Open
mykola-mokhnach wants to merge 2 commits into
appium:masterfrom
mykola-mokhnach:feat/chromedriver-executable-verification
Open

mykola-mokhnach wants to merge 2 commits into
appium:masterfrom
mykola-mokhnach:feat/chromedriver-executable-verification

Conversation

@mykola-mokhnach

Copy link
Copy Markdown
Contributor

Summary

Bumps appium-android-driver to v16 and appium-chromedriver to v11, which verifies ChromeDriver and Microsoft Edge WebDriver executables against a SHA-256 allowlist before running them (appium/appium-android#171).

  • Only builds distributed by Google/Microsoft, and the ones downloaded by the driver itself via chromedriver_autodownload, are run.
  • This applies to appium:chromedriverExecutable and to the executables found in appium:chromedriverExecutableDir.
  • Custom or unlisted executables require the new chromedriver_allow_any_executable server feature (--allow-insecure espresso:chromedriver_allow_any_executable).

Docs: new "Executable Verification" section in the hybrid guide, the new insecure feature, and notes for the two capabilities.

Breaking change

Custom, self-built or unlisted ChromeDriver executables are rejected unless chromedriver_allow_any_executable is enabled on the server.

Note: the docs say "since 11.0.0", please adjust if the release version differs.

…Driver executable verification

BREAKING CHANGE: ChromeDriver and Microsoft Edge WebDriver executables are verified against a
SHA-256 allowlist before they are run. Custom or unlisted executables are rejected unless the
chromedriver_allow_any_executable server feature is enabled.

This branch has not been deployed

No deployments
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