At least as a possible stop gap measure until we have a linux/arm64 browser available. What would be nice is if a) burp would stop extracting the browser tarball, regardless of architecture on linux, and actually check that it is on amd64 first - this would save linux/arm64 users about 340MB of space, since the browser cannot be used and b) check if linux/arm64 and if so, tell users that they will need to use their own browser. I've tried creating a backup of the x86_64 browser directory, and then using rsync to copy a Chromium installation in (and then renaming chromium to chrome), and while this allows for things like launching the documentation and help, unfortunately, after a little while, this simply exits, and unfortunately, there isn't a good error message for why it is crashing.
Burp suite m1 mac upgrade#
When BurpSuite starts for the first time (or after an upgrade which includes a browser upgrade), it extracts the Linux tarball, without any regard to the architecture. I've tried a few things here, to get things to work, but unfortunately, it's just not quite working out.īurpSuite comes with a number of browsers packed with it, namely Linux/x86_64, Windows/x86_64, MacOS/x86_64 and MacOS/arm64 - Chrome is not available (as far as I know) on any other platforms, so unfortunately, there isn't a Linux/arm64 browser packaged in.
We'd love to see better support on arm64 as well.
This is semi related to the other bug about BurpSuite Pro on Kali in a VM on MacBooks with the M1 processor ( )
0 kommentar(er)
