If CNAME settings are used, the CNAME record will be returned if the label in the domain matches, regardless of the DNS query type. You can view a configuration for a polling interface with customized ports in our example configuration file. The Collaborator server's DNS service directs polling requests to the correct interface. To do this, repeat the ssl configuration under both eventCapture and You can use a single TLS certificate for both the interaction and polling interfaces. If you don't include an option, the options in the eventCapture field are used. You can fully customize the polling interface, for example to configure ports or a TLS certificate. To configure a separate polling interface, add a polling field to your configuration file. This enables you to work around firewall restrictions, or control access to the polling function at the network level. You can configure the server to serve polling requests on a different interface. Polling requests - When Burp asks the Collaborator server whether any interaction events have occurred due to the Collaborator payloads.For example, a DNS lookup or an HTTP request. Interaction events - When a target application initiates an interaction with the Collaborator server.

To do this, use the customīy default, the Collaborator server handles both interaction events and polling requests on the same network interface:

You may need to prove domain ownership to obtain a valid certificate. Use this configuration when the Java keytool generates the Certificate Signing Request, and you import the certificate into the Java keystore of the server: Openssl pkcs8 -topk8 -inform PEM -in keys/ -outform PEM -out keys/.pkcs8 -nocrypt Java keytool You also need to convert the keys from the SSLeay format to PKCS8. You can view this configuration in our example configuration file. Make sure you specify the configuration in the correct order: private key, certificate, intermediate certificate(s). Use this configuration when OpenSSL generates the Certificate Signing Request and the CA provides the certificate and intermediate certificate: Two example configurations are outlined below: You also need to update your configuration file to load the certificate. If you are using certificates signed by an internal CA, then you will need to make sure that Java's trust store has the right certificates. If you have purchased a valid wildcard TLS certificate for your domain, you can obtain the certificate from your Certificate Authority (CA), and install it in your Collaborator server. To configure the domain on the self-signed wildcard certificate, use the following configuration: The target application does not validate TLS certificates.You can install the certificate as trusted on the target server.This is generally sufficient in the following situations: If you don't configure a TLS certificate in the configuration file, then a self-signed certificate is automatically generated for you. You need to use a wildcard TLS certificate for your domain name to make TLS connections to the Collaborator server.

If you need any further details or have any questions please contact our Support team. The configurations that are described on this page are examples.

Burp collaborator community edition