Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Type is showing up as "Legacy Java" ??

Roy | Last updated: Oct 25, 2016 04:58PM UTC

Hi, I am just starting to learn about writing extensions for Burp and am using Eclipse/Java. I have built and run my first "Hello World" extension and am wondering why Burp is showing it as "Legacy Java" on the Extender/Extensions tab. Is it because I have added the BurpSuite jar to my project by going to Project->Properties on the top toolbar, selecting "Java Build Path" and on the "Libraries" tab clicking "Add External JARs..." (for debugging purposes). Or does it have something to do with the JDK/JRE I have installed? thanks!

PortSwigger Agent | Last updated: Oct 26, 2016 03:45PM UTC

Burp reports this as a legacy extension because you are loading it by placing it into the classpath when loading Burp. The new way of loading extensions is to compile them as their own JAR, and load them into Burp via the Extender / Extensions tab. The way you are loading your extension is fine, and it will have all the same capabilities as a non-legacy extension. It also means you can debug the extension more easily within your IDE.

Burp User | Last updated: Feb 08, 2018 02:20PM UTC

Something I've noticed now that I'm trying to play with vmware's rest-api, is that it appears that if you start burp with the jarfile that project builds, it will ONLY load the legacy extension, and it will ignore the others, even when trying to load them through the gui.

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