Burp Suite User Forum

Create new post

Use a wildcard certificate with the Burp Collaborator server (polling issue)

ya | Last updated: Sep 15, 2016 02:31PM UTC

Hello, I have the exact same issue as here: https://support.portswigger.net/customer/en/portal/questions/16684743-collaborator-polling-ssl-root-cert I tried what you said: "Configuration of SSL certificates should be the same for the interactions and polling interfaces, so you’ll need to specify the key file and the intermediate / final certificates.". But when I launch the collaborator server, the following issue appear: # ./launch-burp-collaborator.sh 2016-09-15 10:33:43.270 : Only one of the https keystore, hostname or certificates parameters can be specified. Exception in thread "main" burp.jic: Only one of the https keystore, hostname or certificates parameters can be specified. at burp.qrf.c(Unknown Source) at burp.qrf.b(Unknown Source) at burp.tzd.<init>(Unknown Source) at burp.StartBurp.main(Unknown Source) Here is a snippet of my configuration: { "eventCapture": { "https": { "port" : 443, "certificateFiles" : [ "/…/ssl/burpc.key.pkcs8", "/…/ssl/burpc.crt", "/…/ssl/COMODORSADomainValidationSecureServerCA.crt" ] } }, "polling" : { "https": { "port" : 9443, "hostname" : "polling.9w4.fr", "certificateFiles" : [ "/…/ssl/burpc.key.pkcs8", "/…/ssl/burpc.crt", "/…/ssl/COMODORSADomainValidationSecureServerCA.crt" ] } }, […] } If I remove the "certificateFiles" from the "polling" node, the server use an auto-signed certificate and Burp Suite is not able to fetch the polling server via HTTPS. Do I miss something? Thanks in advance!

PortSwigger Agent | Last updated: Sep 19, 2016 08:20AM UTC

You need to remove the "hostname" line from your "polling" section. The hostname configuration tells Burp to self-generate a cert with that hostname, and isn't compatible with the "certificateFiles" option.

Burp User | Last updated: Sep 30, 2016 09:27AM UTC

Hello Dafydd, Many thanks for your help, it works like a charm!

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.