Burp Suite User Forum

Create new post

partial JSON config files

Clayton | Last updated: Sep 21, 2016 01:47PM UTC

Currently when starting a new burp project and loading it with a config file, you have to have every option filled in the JSON, otherwise it'll leave that field as blank in the new project. I'd really like it if you could just have your JSON config file contain what you wanted different ( like targets excluded from scope, regex to exclude on scanners, private burp collab server, etc), and it would apply the default settings for all other fields. That way, if the default values change or new ones are added, you don't have to change your JSON config.

PortSwigger Agent | Last updated: Sep 21, 2016 01:52PM UTC

Thanks for this feedback. We'll look into fixing Burp so that any undefined configs in a partial config file revert to their default values. In the meantime, there are two workarounds: 1. In the startup wizard, select to use project defaults, and then load your partial config file via the Burp menu. This will leave any undefined configs with their default values. 2. Launch Burp from the command line and use multiple --config-file options to specify first a full config file with default values, and second your partial config file. These will be applied in order, leaving any undefined configs in your partial file with their default values.

PortSwigger Agent | Last updated: Nov 29, 2016 04:50PM UTC

As of today's release (1.7.13) we have fixed the issue with partial configuration files causing blank config values. Thanks again for your feedback.

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