Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save extension settings into project file #42

Open
aph3rson opened this issue Oct 19, 2023 · 0 comments · May be fixed by #44
Open

Save extension settings into project file #42

aph3rson opened this issue Oct 19, 2023 · 0 comments · May be fixed by #44

Comments

@aph3rson
Copy link

Previously, Burp did not allow for easy state tracking for extensions across restarts of Burp/reloads of the extension/reloads of the project. This meant that extensions had to either be reconfigured across every reload, or do hacky things to track extension state as a bogus request in the sitemap.

However, Burp now supports the saveExtensionSetting and loadExtensionSetting API methods, which allows saving simple key/value pairs associated with the extension. These settings are durable across extension reloads, project reloads, and Burp restarts.

It'd be great if AWSSigner supported these methods, and saved extension state into the project file itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant