-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
null pointer when launching interpretter from the command line #12
Comments
@mwielgoszewski please could you weigh in on this? |
The old run.py script was for versions of Burp before the new Extender API was introduced, where you had to manually specify arguments on the command line. The latter approach, or in your terms, "workaround", is actually the preferred way to load the the jython-burp-api. |
Oh that's unfortunate... I was hoping to use the run.py for automated testing. Thanks for the update. |
@nitrocode I'm trying to automate testing using Burp from the blog and was stuck with the same error as yours - I'm executing the command in EC2 instance and I have no option to use the UI interface of Burp. Can you please suggest if there is any possible workaround for the automated testing with Burp. TIA |
@anil10032 Any solution on this issue? |
Command:
Then when Burp loads I select to use a temporary project and use Burp defaults. After I click on Start Burp that's when it shows me:
Nothing else is outputted but this seems to be a good workaround:
Load Burp
Navigate to Extender and manually load Lib/burp_extender.py
The text was updated successfully, but these errors were encountered: