Re: [Burp-users] Config: Source wildcarded files from a directory

[Graham K. <gr...@gr...>]

On Wed, Mar 04, 2015 at 12:27:02PM +0100, Ziirish wrote:
> * On Wednesday, 04 March 2015 12:22, Graham Keeling <gr...@gr...> wrote:
> > 
> > Hello,
> > 
> > I'm not sure I can quite see how it makes what you are doing easier, but
> > I have nothing against expanding the existing '. /path/to/include' feature
> > to be glob patterns, so go ahead. :)
> 
> Hi,
> 
> I guess I can give it a shot as part of the work I have to do on the
> configuration tests.
> I plan to work on it by the end of the month if that's soon enough for both of
> you.

Hello,

In the last week, I have made significant changes/improvements to the conf
code in git branch 'conf_nextgen' (only just missing the last 2.0.x release).

There are now unit tests starting to build up in the 'utest' directory.

Each config now has an enum value, a field name, and a type. Rather than the
config being a single massive struct, it is now an array of these
enum/field/type triplets.

This means that you can now do cool things like this:

burp -t (shows the client config from /etc/burp/burp.conf):

                        conffile: /etc/burp/burp.conf
                            mode: client
                        lockfile: 
                         pidfile: /tmp/burp.client.pid
                          syslog: 0
                          stdout: 1
                progress_counter: 1
                     ssl_cert_ca: /etc/burp/ssl_cert_ca.pem
                        ssl_cert: /etc/burp/ssl_cert-client.pem
                         ssl_key: /etc/burp/ssl_cert-client.key
                ssl_key_password: password
                     ssl_peer_cn: burpserver
                     ssl_ciphers: 
                 ssl_compression: 5
(snip)


burp -t -c /etc/burp/burp-server.conf (shows the server config):

                        conffile: /etc/burp/burp-server.conf
                            mode: server
                        lockfile: 
                         pidfile: /var/run/burp.server.pid
                          syslog: 0
                          stdout: 1
                progress_counter: 0
                     ssl_cert_ca: /etc/burp/ssl_cert_ca.pem
                        ssl_cert: /etc/burp/ssl_cert-server.pem
                         ssl_key: /etc/burp/ssl_cert-server.key
                ssl_key_password: password
                     ssl_peer_cn: 
                     ssl_ciphers: 
                 ssl_compression: 5
                            user: 
                           group: 
                       ratelimit: 0
                 network_timeout: 7200
               client_is_windows: 0
                    peer_version: 
                        protocol: 1
                         address: ::
                            port: 4971
                  status_address: ::1
                     status_port: 4972
                       directory: /home/graham/isos/burp
                timestamp_format: %Y-%m-%d %H:%M:%S
                   clientconfdir: /etc/burp/clientconfdir
                      ssl_dhfile: /etc/burp/dhfile.pem
(snip)



burp -t -c /etc/burp/burp-server.conf -C testclient (shows the overridden
server side config for a particular client):

                        conffile: /etc/burp/burp-server.conf
                          syslog: 0
                          stdout: 1
                progress_counter: 0
                            user: 
                           group: 
                        protocol: 1
                       directory: /home/graham/isos/burp
                timestamp_format: %Y-%m-%d %H:%M:%S
                   clientconfdir: /etc/burp/clientconfdir
                  directory_tree: 1
                  password_check: 1
                   manual_delete: 
            monitor_browse_cache: 0
                       incexcdir:
                         include:
(snip)



There are rough edges, but it is already very useful.

So, if you are going to be doing any work related to testing/reading configs,
you should make sure you are doing it on top of this latest code. I will
be merging it back to branch 2.0.15 in the next few days.

Maybe you can remind me what you needed to have working? Since I am already
fiddling with this stuff, maybe it is a good time for me to do it now.