Bapps folder and non BApp store extensions
I have a question on how Burp installs extensions from BApp store vs local extensions. It looks like for ones installed from the store, Burp stores them under the bapps folder. However for locally sourced ones, it has a zip file in the temp directory. Why's is like this?
I'm asking this because, I need to package a Burp extension which has the UI in Java but uses Python/Jython modules that need to be added to Jython's python.path. It doesn't work if the modules are available only as .zip. I'm also not thinking of having the users manually install these python modules to their Jython lib folder since I feel it's too much overhead.
Is there a solution you suggest for this requirement or know of any other means of distributing/packaging the extension so jython.jar can find it dynamically? TIA
Hi Venka, can you clarify what you mean by locally sourced ones?
Are these extensions that you are loading through ‘Manual Install’ on the BApp store, or extensions you are adding in the ‘Extensions’ tab?
Hi Venka, due to the way that we package and install BApp extensions within Burp Suite, it’s not possible to have a mixture of Java & Python modules within a BApp as we package them differently depending upon if it’s a Java, Python or Ruby extension.
Our recommendation would be to convert your UI and extension to be completely Python based and then list your modules within a requirements.txt file, that way we can package them up within a BApp extension so then your users will have an easy installation process.