Closed noraj closed 2 years ago
~/.cme/cme.conf
is the one and only one :)
/usr/lib/python3.10/site-packages/cme/data/cme.conf
is the default config when you install cme and you don't have a conf in ~/.cme/cme.conf
the conf will be copied in to ~/.cme/cme.conf
. So if you modify /usr/lib/python3.10/site-packages/cme/data/cme.conf
, just delete the ~/.cme/cme.conf
and relaunch cme
No it's not the same as #519.
Describe the bug
Parsing the config fails.
To Reproduce
In #519 the workaround was to disable bloodhound by setting
bh_enabled = False
but here I have the default config file where it's already disabled./usr/lib/python3.10/site-packages/cme/data/cme.conf
yet the config parser says the
BloodHound
section doesn't exist when it's is and the config file is at the right place.Crackmapexec info
Solution
~/.cme/cme.conf
was set too but without[BloodHound]
and have precedence over/usr/lib/python3.10/site-packages/cme/data/cme.conf
PS : I log this just as knowledge base.