Closed github-notafake-contact closed 10 months ago
Thanks for the detailed report! This is not your fault; it's an aggravating bug that's been eluding me for some time. I will take a closer look and see if I can track it down.
TrustedSec sends their love 😘
Right back at you 😌🙏
Found it! This was a bug in passivetotal
leftover from the async migration. A fix has been pushed: https://github.com/blacklanternsecurity/bbot/pull/831.
You rock! Thanks
I have consistently gotten this error every time I run BBOT for the past few months. Not sure if it's something I'm doing wrong, but this error has been persistent through multiple installs over the past ~ 2 or 3 months. Use BBOT pretty consistently for work during pentest engagements (TrustedSec sends their love 😘).
The error:
Things I have tried:
pip install bbot
pipx install bbot
I've attempted to rule out if the issue was stemming from my Ubuntu VM, so I launched two AWS EC2 instances and installed BBOT on those. One instances was
t4.micro Ubuntu 22.04 Server
and the otherm4.large Ubuntu Server 18.04
. Again, same error both times.There was a time when I didn't get this error. However, that was months ago and I don't remember what version was installed BBOT or what my config file looked like...
Here is my latest install attempt tried today on a brand new EC2 instance running Ubuntu Server 22.04:
NOTE: I run ZSH instead of BASH. Unsure if this is relevant but still noting here just in case.
NOTE: I use pyenv for all Python related things. Every Python tool gets its own virtual environment (e.g.
Impacket
,Scapy
,SubBrute
,Frida
,Requests
, etc...) and have had little to no issues. That said, I'm not ruling out pyenv as being the issue so I'll include how I setup my BBOT environment as well.Complete Environment Setup and BBOT Install:
The entire output:
I'm also not sure why the config files are loaded multiple times. I noticed this started happening about a month ago I believe.
At this point I'm not sure what is causing the issue. I've also uploaded the debug.log file in case that helps.
debug.log