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 and Load from config file #16

Closed
danielthatcher opened this issue May 31, 2018 · 6 comments
Closed

Save and Load from config file #16

danielthatcher opened this issue May 31, 2018 · 6 comments
Assignees

Comments

@danielthatcher
Copy link
Contributor

It would be helpful to be able to save and load a set of replacements from a config file that's independent of burp's state.

This would probably be useful for quite a few situations, but as an example, I'm currently using AutoRepeater to aid with SQLi testing, and each test I have to set up quite a few replacements manually. It would be much quicker to be able to load these in from a config file.

@justinmoore
Copy link
Collaborator

hey @danielthatcher,

I completely agree. This bit of functionality I wanted to add in the near future with the goal of also providing some loadable configs for folks to pull from the git repo as examples.

@justinmoore justinmoore self-assigned this Jun 4, 2018
@justinmoore
Copy link
Collaborator

I'm working on this now.

@justinmoore
Copy link
Collaborator

AutoRepeater does this now. Let me know if there's any issues with it.

@danielthatcher
Copy link
Contributor Author

Finally got a chance to play around with this at work (hence commenting on this a month later - sorry about that), and it's to be working well. Thanks for implementing it.

A colleague and I started playing around with building up some configs, and one thing that we noted is that it might be easier if the configs were stored as JSON rather than Base64 encoded JSON as this would work better with version control. You mentioned that you might also like to have some configs for people to pull in from the git repo, so I believe it would help there too.

@justinmoore
Copy link
Collaborator

hey @danielthatcher,

I agree that it doesn't make a whole lot of sense to store the configs in based64ed JSON. The only reason it's like that is because I wasn't sure how I was going to store the files at the time I was writing it and never got around to fixing it. I'll change it now to support both to make handwriting configs a bit easier.

Thanks,
Justin

@justinmoore
Copy link
Collaborator

justinmoore commented Jul 5, 2018

hey @danielthatcher,

Just to close the loop on this, I've changed the config file format to be JSON instead of Base64 encoded JSON. AutoRepeater will gracefully handle the transition if you have any existing config files.

Thanks,
Justin

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

No branches or pull requests

2 participants