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
We only store burpference interactions with a model in the projects file via raw HTTP request/responses + evals etc as well as "Burp Issues"
Proposed Solution
It'd be awesome to store this locally in a DB which gives the user the retention flexibility and is not dependent on copying and pasting the info out of Burp if needed to be shared externally
Alternative Solutions
NA
Use Case
A local DB in the burpference folder is probably the easiest win-now approach
Additional Context
NA
Implementation Ideas
Similar ideas to how any python code stores and adds to a SQLlite DB or other database storage format
The text was updated successfully, but these errors were encountered:
Problem Description
We only store
burpference
interactions with a model in the projects file via raw HTTP request/responses + evals etc as well as "Burp Issues"Proposed Solution
It'd be awesome to store this locally in a DB which gives the user the retention flexibility and is not dependent on copying and pasting the info out of Burp if needed to be shared externally
Alternative Solutions
NA
Use Case
A local DB in the
burpference
folder is probably the easiest win-now approachAdditional Context
NA
Implementation Ideas
Similar ideas to how any python code stores and adds to a SQLlite DB or other database storage format
The text was updated successfully, but these errors were encountered: