Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Create extender jar using burpsuite.jar in classpath

Bort_Millipede | Last updated: Dec 16, 2016 06:43AM UTC

Hi, I had a question regarding the process for properly building (compiling and creating jar files) Java burp extensions. According to the normal process for this, the Extender interface files should be exported from within Burp in the Extender tab. Then the extension can be compiled and a jar file created using commands such as "javac -d build burp/BurpExtender.java" "jar -cf extender.jar -C build .". This will compile the Extender by also compiling the exported interface files, then will create a jar containing the BurpExtender.class file as well as all the compiled interface .class files. My question is: rather than following the extra step to export the interface files, could the extender be compiled/jar created using the following commands?: "javac -cp burpsuite_free_v1.7.13.jar -d build burp/BurpExtender.java" "jar -cf extender.jar -C build .". This eliminates the need to export the Extender interface files and creates a working extension jar file (one that does NOT contain the interface .class files). Is there any issue with creating extension jar files using this process? Does the fact that the created jar files do not contain the interface .class files create any potential problems? Thanks in advance.

PortSwigger Agent | Last updated: Dec 16, 2016 09:54AM UTC

We suggest you try loading your extension into Burp after compiling it with your proposed command. If everything is working, then it sounds fine.

Burp User | Last updated: Dec 20, 2016 10:30PM UTC

HI Bort, You could try using the Burp Suite Utils package, which includes the Extender interfaces: https://github.com/augustd/burp-suite-utils It is a Maven project, so you simply need to include the project in your pom.xml. There are instructions provided for using the Maven Shade plugin to construct a final jar which includes all your dependencies.

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