Skip to content

Conversation

ohmer1
Copy link

@ohmer1 ohmer1 commented Jan 20, 2023

I added support for custom content in the client's configuration file. My use case was to be able to add a custom include to a client without having to define a new profile just for this addition. To use that feature, just add a content key when defining a client in burp2_add_manual_clients. The content key is of course optional, so this shouldn't break anything.

Example:

burp2_add_manual_clients:
  - name: client_name
    profile: profile name to use (optional), default: profile_lnxsrv (these files are in incexc/ dir).
    password: client_password (optional), default: burp_client_password var
    content: 
      - 'include = E:/'
  - name: second_client

@ohmer1 ohmer1 changed the title Add support for custom client in the client's configuration file Add support for custom content in the client's configuration file Jan 20, 2023
@pablodav
Copy link
Contributor

Thanks you!
This looks very good, I have some issues with the automatic tests that I need to troubleshoot before merging.

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

Successfully merging this pull request may close these issues.

2 participants