The software allows you to switch between them and run different versions for different threads.
To do this, use the "Browser Settings" action with the "Browser Version" parameter.
The actions "Get list of available browser versions" and "Get current browser version" have also been added.
It is planned to make a new release with a browser update every month.
In best case scenario, users will receive BAS version shipped with the three latest versions of Chrome 2 weeks after the browser release.
For example, if Chrome version 120 is released on December 1, then BAS version should be released in the middle of December and will contain browser versions 120, 119 and 118.
But right now it is only intention, it is not 100% guaranteed that such schedule will be maintained.
BAS version 25.6.0 ships with two versions of Chrome: 113.0.5672.64 and 111.0.5563.65.
Added filtering option "Maximum browser version" when getting fingerprint.
If you use the keyword "current" for the minimum and maximum browser version, then the resulting fingerprint will always match the real browser version
The vast majority of fingerprints are collected for x64 systems. Taking into account that BAS used x86 browser build previously, this inconsistency could be detected.
In fact, although x86 support is formally retained, we strongly advice against using OS with this architecture. It may contain bugs, including critical.
To ensure that proxy works correctly on x64 build, the tunneling library had to be updated.
Tweaking the Fingerprints.StackSizeDiff parameter is no longer necessary.
In this version, additional measures have been taken to improve the authenticity of the browser:
Browser build is now official.
Additionally, you can remove these options from the chrome_command_line.txt file:
The absence of this feature can be detected. For example, one well known test uses this technique to distinguish between Chromium and Chrome.
Safe browsing support can be disabled on the settings page or by using the "Browser Settings" action
Browser components support can be disabled on the settings page or by using the "Browser Settings" action
Components will not be displayed on the chrome://components/ page, but they will be used by the browser.
There is at least one site that blocks a browser that doesn't use http3 and another that changes behavior when http3 is not present.
http and non-udp sock5 proxies should automatically use the old version of the protocol.
If you experience problems loading or displaying the site on the new version, you need to try disabling QUIC, if it helps, be sure to send the proxy, site and sequence of actions to [email protected]
Some methods for detecting BAS.
Fixed BAS detection on one site.
Fixed another method that could potentially lead to detection.
Proxy for profile creation.
BAS blocks any requests to the network between the time the profile was created and the time when proxy was set. This is done so that real ip is not used for requests to Google services.
In the new version, _set_proxy_for_next_profile method is available, it allows you to change this behavior:
Fixed issues with PerfectCanvas generation for several methods.
Better emulation for input events on "tel" input type on Android.
Other fixes.
25.6.1
Fixed issues with DPI emulation.