Closed mkilijanek closed 4 years ago
Version taken from contents of file:
Kili,
Good morning. How are you?
I've just replied you on Twitter and, according to my test here (just now), I haven't faced any problem. Please, could you confirm whether you edited the configmalw.py in /usr/local/lib/python3.8/dist-packages/malwoverview/conf/ (or similar) directory?
Have an excellent day.
My OS: Fedora 31 (Linux kili 5.3.16-300.fc31.x86_64; Security Spin + KDE Plasma; RPM Fusion enabled)
(malloverview) ➜ bin pip --version pip 19.3.1 from /home/kili/VENV/malloverview/lib/python3.7/site-packages/pip (python 3.7) (malloverview) ➜ bin python3 --version Python 3.7.5
Steps I performed:
I think result might differ between Linux distros :(
Config file location is in bin directory of Virtualenv. No directory structure as you described is observed.
Dear mkilijanek,
The problem is not the the different of OS versions, but the final directory structure. In a nutshell, you were using the "wrong" configmalw.py because the installation has been "virtualized and sourced".
Please, try to follow the same steps below and let me know whether everything goes right.
Have an excellent day.
Alexandre.
Due to no further comments, I'm closing the issue.
Config file appears not being used in pip version of malwoverview (2.0.8), which forces end user to provide API keys directly in malwoverview to work with tool. (In my case it worked as temporary workaround)