You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing the application, I noticed that Java resource loading failed under circumstance. This leads to issues where the plugins may try to load a file containing for example, a list of words and therefore silently running with an empty wordlist. The end result is that the plugin fails silently under certain conditions which is not ideal.
I think this triggers when the jar file for an extension changes without restarting burp. The workaround for now is to restart Burp whenever we recompile our jar plugins.
Here's an example call that fails:
src/burp/Utilities.java:249: Scanner s = new Scanner(getClass().getResourceAsStream("/functions"));
src/burp/Utilities.java:256: Scanner params = new Scanner(getClass().getResourceAsStream("/params"));
A better solution would be to modify the Java source code to fetch these resources from the hard-drive to a location within our Python repository, or putting in an assertion that crashes the plugin whenever this happens. This is slightly annoying when developing so I haven't put it in place yet.
The text was updated successfully, but these errors were encountered:
While testing the application, I noticed that Java resource loading failed under circumstance. This leads to issues where the plugins may try to load a file containing for example, a list of words and therefore silently running with an empty wordlist. The end result is that the plugin fails silently under certain conditions which is not ideal.
I think this triggers when the
jar
file for an extension changes without restarting burp. The workaround for now is to restart Burp whenever we recompile ourjar
plugins.Here's an example call that fails:
A better solution would be to modify the Java source code to fetch these resources from the hard-drive to a location within our Python repository, or putting in an assertion that crashes the plugin whenever this happens. This is slightly annoying when developing so I haven't put it in place yet.
The text was updated successfully, but these errors were encountered: