Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

macOS Mojave - Burp suite DMG doesn't open

ashok | Last updated: Sep 26, 2018 06:16AM UTC

“burpsuite_pro_macos_v1_7_37.dmg” is damaged and can’t be opened. You should move it to the Trash. Is burp suite compatible with Mojave?

Liam, PortSwigger Agent | Last updated: Sep 26, 2018 09:51AM UTC

Hi Ashok Thanks for your message. We've investigated this issue and have reproduced the problem. There seems to be a problem with mounting the .dmg file. As a workaround you can use the .jar version of Burp on Mojave. Alternatively, you can mount the file using the "hdiutil attach" command: Downloads liam$ hdiutil attach burpsuite_pro_macos_v2_0_06beta.dmg Then run the installer. Please let us know if you need any further assistance.

Burp User | Last updated: Sep 29, 2018 07:56PM UTC

This still won’t work for me...

Liam, PortSwigger Agent | Last updated: Oct 01, 2018 07:15AM UTC

Olle, what issue are you having? Have you tried the Burp .jar file?

Burp User | Last updated: Oct 01, 2018 12:55PM UTC

Still the same with .dmg and .jar - even when you manually mount the .dmg file the installer will not be executed.

Liam, PortSwigger Agent | Last updated: Oct 01, 2018 01:10PM UTC

Maz, we haven't noted this issue with the .jar file. Try right clicking on the file and opening with Jar Launcher.

Burp User | Last updated: Oct 01, 2018 02:23PM UTC

I have the same issue. Neither the Community dmg (which I tried first before applying for a test license for the Pro version) nor the Pro dmg will install in my macOS Mojave machine. The Jar file opens, but that is not a long-term practical solution because I must disable Java to use certain applications.

PortSwigger Agent | Last updated: Oct 01, 2018 02:56PM UTC

Sorry to hear people are having continued issues. We will be releasing updated dmg files that work with Mojava when the are ready. In the meantime, manually mounting the dmg works for me: 1) hdiutil attach burpsuite_community_macos_v1_7_36.dmg 2) Locate the mount BurpSuitePro or BurpSuiteCommunity in Finder 3) Double click the installer If that doesn't work, then the only workaround for now is to use the standalone jar.

Burp User | Last updated: Oct 01, 2018 08:08PM UTC

Same issue for me. No chance to install Burp (Community) v1.7.36. After downloading the Jar file I can start Burp with the command 'java -jar burpsuite_community_v1.7.36.jar'. On my machine the latest Java JDK/JRE 11 is installed on macOS Mojave. Hope this helps for you too. Greets from Duesseldorf Christoph

Burp User | Last updated: Oct 04, 2018 10:07PM UTC

Same issue for me. Mounting it with hdiutil won't let it execute and install.

Liam, PortSwigger Agent | Last updated: Oct 05, 2018 08:59AM UTC

Philippe, could you try using the .jar file until we get this fixed?

PortSwigger Agent | Last updated: Oct 05, 2018 09:00AM UTC

The Burp 2.0.8 beta release now works with Mojave. We'll be issuing updates to 1.3.37 Pro and 1.3.36 Community in due course.

Burp User | Last updated: Oct 10, 2018 12:10AM UTC

Same here, doesn't install on my Mojave, gives this error, “burpsuite_community_macos_v1_7_36.dmg” is damaged and can’t be opened. You should move it to the Trash.

Burp User | Last updated: Oct 10, 2018 05:33AM UTC

Fresh Mojave install here, same issue. DMG won't mount by clicking, mounting it using hdiutil works the the .app does not launch anyway. This is an issue with the GateKeeper, code signature seems to be invalid on the Burp install .. just do "sudo spctl --master-disable" to disable GateKeeper, install Burp and re-enable right after with "sudo spctl --master-enable". Crappy workaround but works. Adding exception with "spctl --add" does not seem to work :(

Burp User | Last updated: Oct 30, 2018 12:15AM UTC

Paul - Might I ask you what you changed to make that work? I ask because my company has an app that's started receiving this error since upgrading to Mojave and I'm baffled as to why.

PortSwigger Agent | Last updated: Oct 30, 2018 10:46AM UTC

Hi Alan, We upgraded install4j which we use to build our release packages. I'm not sure what change they made, but they may be willing to tell you.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.