Burp Suite User Forum

Create new post

Cannot load saved user options with --config-file in command line

Peter | Last updated: Dec 08, 2016 06:06AM UTC

Dear Guys, My problem: I saved the user options into some JSON format configuration file, and then I can load it from GUI successfully, all the configured extensions are there, it's very good. However, I cannot load the configurations by starting Burp-Suite [latest version, 1.7.13, professional] from command line with "--config-file", all extensions are gone...And no clues there even with the "--diagnostics"... java -Xmx4G -jar burpsuite_pro_v1.7.13.jar --config-file="burp_user_options.json" --diagnostics My question: Could you please help me check if anything wrong in my way to load the user options config file? Or how can I solve this problem? I'm waiting your response online, and thanks a lot! Regards, Peter

PortSwigger Agent | Last updated: Dec 08, 2016 09:21AM UTC

The --config-file option is only for project-level settings. User-level settings cannot be loaded with this option, and you'll need to load those via the Burp menu when you move to a new machine. Once loaded, user-level settings are automatically persisted across launches of Burp (provided you shut down gracefully) so you won't need to load them again.

Burp User | Last updated: Dec 09, 2016 02:44AM UTC

Thanks a lot for your message! My Problem: And the problem is burp will crash sometime or terminated forcibly sometime. After rebooting, all the extensions are there but disabled. We're trying to automate the burp-suite in our scanning with help of our extension, in such case manual operations to enable from GUI is necessary and which is not acceptable in automatic testing. My Questions: The extension information are serialized in user settings but not the project settings. Then according to your answer above, it means that no way to reload user settings from command line currently, right? Wait for your answer online, and thanks very much! Regards, Peter

PortSwigger Agent | Last updated: Dec 09, 2016 12:19PM UTC

That is currently the case, yes. At some point, we might provide a way to specify an extension to load on the command line. If you have run Burp once with extensions loaded, and then gracefully shut it down, then they should continue to reload, even if Burp sometimes terminates abnormally. Let us know if you identify a way to reproduce a problem there.

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