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
I have been testing since 2 weeks ago and today after full updating, more features were added, but one really important disappeared . The possibility to have multiple running instances of BadK, all of them with independent sqlite files, with autosave on during the work, also independent from one another.
Atm i can only save to the default sqlite file /tmp/badkarma.sqlite.
His this a bug?
Regards.
R
The text was updated successfully, but these errors were encountered:
Hi re8el,
Thank you for your feedback,
I'm unable to reproduce this issue, multiple instances are working for me,
did you try using the "--session" argument?
You can run multiple instances of BadK using different session files,: ./badkarma.py --session /tmp/test1.sqllite & ./badkarma.py --session /tmp/test2.sqllite
Using your recommendation ./badkarma.py --session /tmp/test1.sqllite & ./badkarma.py --session /tmp/test2.sqllite all works ok even reopening and new scans get added to the console.
But if i just open badk has ./badkarma.py them in the console, go to load the session file for a an already created session file that already has machines from past scans, doing new scans i cannot have the new scans results added automatically. This was working and now it doesnt.
Hi,
First let me congrat you on a great tool!
I have been testing since 2 weeks ago and today after full updating, more features were added, but one really important disappeared . The possibility to have multiple running instances of BadK, all of them with independent sqlite files, with autosave on during the work, also independent from one another.
Atm i can only save to the default sqlite file /tmp/badkarma.sqlite.
His this a bug?
Regards.
R
The text was updated successfully, but these errors were encountered: