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

Calling callbacks.exitSuite(false) causes extension that called it not be loaded next time

David | Last updated: Apr 21, 2020 11:41PM UTC

Hi, I'm making an extension at the moment, and one of the things I would like to do is be able to nicely exit burp in specific conditions. When calling callbacks.exitSuite(false), burp does exit nicely, but the next time I start burp, my extension is loaded, but not enabled. As part of my startup paramters, I am also loading a user config json that includes the following. "extensions":[ { "errors":"ui", "extension_file":"<path_to_burp_extension>", "extension_type":"java", "loaded":true, "name":"<extension name>", "output":"ui" } ] Is there a way of existing nicely without unloading the extension? I can run a System.exit(0);, which does exit, and the extension does load next time, but it leaves temporary files, and who knows what other mess. Thanks

David | Last updated: Apr 21, 2020 11:44PM UTC

Sorry, I'm just putting a second response to this, I realised that I got the terms "loaded" and "enabled" a bit confused. The extension will appear in the extensions list(eg it appears in the Burp Extnesions list), but the "loaded" tick box is not ticked after a exit using the callbacks.exitSuite(false)

Hannah, PortSwigger Agent | Last updated: Apr 22, 2020 11:22AM UTC

To clarify, even with the user config file being included as part of the startup arguments, your extension is still not loaded? After installing and loading your extension and before your extension closes Burp Suite, did you manually close it yourself (confirming that you want to close all windows)?

David | Last updated: Apr 23, 2020 12:52AM UTC

Hi Hannah, Thanks for your response, I've got it sorted, I think I just needed to walk away and come back the next day. I spent a bit more time this morning looking at this, and I had two problems, one with my json file, and one with using the --config-file="" option instead of the --user-config-file="".

Hannah, PortSwigger Agent | Last updated: Apr 23, 2020 11:04AM UTC