Navigation Menu

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

[Feature Req] Override config options by cmdline args #727

Closed
melak opened this issue Jun 24, 2018 · 5 comments
Closed

[Feature Req] Override config options by cmdline args #727

melak opened this issue Jun 24, 2018 · 5 comments

Comments

@melak
Copy link
Contributor

melak commented Jun 24, 2018

My particular use case is I have several burp servers dropped here and there, then as my notebook is connected to a particular network (think friends, family, whatnot), backups are taken.

Currently this involves replicating the client config file basically only for changing the server directive in them. The situation would be much simplified if I could override server from the command line. There could be some other options where overriding would make sense, although browsing through my configs, there's nothing else I could think of (someone else probably will, though).

@deajan
Copy link
Contributor

deajan commented Jun 25, 2018

I think @pablodav has a powershell script that does something like that.

@pablodav
Copy link
Contributor

pablodav commented Jun 25, 2018

My script https://github.com/pablodav/burp_eclient
Doesn't change server, it changes speed and other settings in config before launching burp.

The idea could be used to implement what @melak explains, but probably there are other better ways to do it too.

But I think implementing change of server based on identified network connection is not good feature to add to burp, as it could complicate things necessarily.

The simplest way:

  • Create 3 different configurations for each network
  • Create 3 different schedule jobs for each config

We do this way and is a very stable one.

You can also log into different log files in this way.
The clients will work when server is reachable.

Option 2:

Setup your script that changes the server in .conf file, like burp_eclient does.
This is not stable way, not recommended at all.

Option 3:

Setup the server in dns in each network.
Use same name on each network
So when working at home / office / etc, client will reach the server based on its name.
You can do similar trick having modified hosts (unstable way).

@deajan
Copy link
Contributor

deajan commented Jun 26, 2018

You may also setup a unique task which will launch a script that detects the current network (whatever fits, ping, detect subnet or else), and then launches a burp instance with a network specific configuration file, eg burp -c burp-network.conf depending on the detected network.

@grke
Copy link
Owner

grke commented Jul 14, 2018

Without thinking much about it, I do think it would be nice to override any config option on the command line.

Something like:

burp -o 'server=1.2.3.4' -o 'port=5071'

@grke
Copy link
Owner

grke commented Aug 26, 2018

Now in git master.

@grke grke closed this as completed Aug 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants