Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

It seems like some release of the Jar files have the MacArm64 Chrome BurpBrowser and others don't

DAVID | Last updated: Jun 13, 2023 07:23PM UTC

Using the Jar version on Mac there are inconsistencies with the embedded browser. Looking inside the Jar file on some versions there is an Arm64 browser and then some don't, even though I get an error that says unpacking the BurpBrowesr binary failed because the chromium-macosarm64-version.zip archive was not found. Then again, some versions have the binary.

Russell | Last updated: Jun 14, 2023 12:27AM UTC

yep - just updated burp pro and I can no longer launch the embedded browser using the jar version on macos arm64 with error message "net.portswigger.devtools.client.impl.connection.local.Zb: Unpacking the BurpBrowser binaries failed because the chromium-macosarm64-114.0.5735.106.zip archive was not found on the classpath!" checking through the last few release JAR files, it looks like chromium-macosarm64-${version}.zip stopped being included in the JAR builds as of v2023.4 - the same release linux arm64 support landed, which is also not present in the JAR releases. since the JAR release ships a build of *every* platform browser it's obviously larger than the platform-specific installers, but can we not regress platform support? or at least drop macosx64 and retain support for macosarm64?

Ben, PortSwigger Agent | Last updated: Jun 14, 2023 08:14AM UTC

Hi both, To confirm, we now have dedicated installation files for both Mac M1/ARM and Linux ARM64 machines so the decision was made to remove the requisite embedded browser files from the standalone Jar file. If you wish to use the later versions of Burp on machines with this architecture then you would need to obtain the specific installation file rather than the standalone Jar.

Russell | Last updated: Jun 15, 2023 06:32AM UTC

Hi Ben - if this was an explicit decision then so be it, but I don't understand the reasoning. You also provide dedicated installers for x86 Windows, x86 MacOS, and x86 Linux, but haven't removed all those platform browsers from the jar release.

Dominyque, PortSwigger Agent | Last updated: Jun 16, 2023 09:36AM UTC