Burp Suite User Forum

Create new post

loadExtensionSetting() does not see extension options any more

kyprizel | Last updated: Jan 24, 2017 05:24PM UTC

I was using callbacks.loadExtensionSetting() to load my extension settings from config file. In json it looked like: { "user_options":{ ... "extender":{ "extensions":[ { "errors":"console", "extension_file":"/path/to/my/ext/burp-XXXX-SNAPSHOT.jar", "extension_type":"java", "loaded":true, "name":"...", "output":"console", "initial_url": "https://kyprizel.net/" } ] } } } and I started burp with --config-file options. Starting from version 1.7.16 config-file does not see extension any more so I had to switch to --user-config-file. Now extension loaded but callbacks.loadExtensionSetting("initial_url") returns nil. What section is used for per-extension configs now?

PortSwigger Agent | Last updated: Jan 25, 2017 09:15AM UTC

Thanks for this report. We did make some changes to the way user settings are handled in 1.7.16, to support the new command line option. We’ll investigate whether this has broken the way that extensions’ custom settings are handled. We’ll let you know if we need any further information.

Mike, PortSwigger Agent | Last updated: Jan 25, 2017 03:12PM UTC

Hi Eldar No changes have been made to the callbacks.saveExtensionSetting() / callbacks.loadExtensionSetting() feature so it's strange that you're seeing this problem. One explanation would be if the "name" field in the user-config-file JSON was inadvertently modified. In this case the settings loader would try to locate settings for an extension with the new name and wouldn't find the ones saved under the original name. Similarly, if the extension makes use of the callbacks.setExtensionName() feature to change the extension name, the same situation could arise. Could you please check if either of these apply and, if not, get back to us so we can investigate further?

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