alexandreborges / malwoverview

Malwoverview is a first response tool used for threat hunting and offers intel information from Virus Total, Hybrid Analysis, URLHaus, Polyswarm, Malshare, Alien Vault, Malpedia, Malware Bazaar, ThreatFox, Triage, InQuest and it is able to scan Android devices against VT.
https://github.com/alexandreborges/malwoverview
GNU General Public License v3.0
2.85k stars 439 forks source link

configmalw.py is not used in version 2.0.8 #7

Closed mkilijanek closed 4 years ago

mkilijanek commented 4 years ago

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) 2019-12-30_13-32

mkilijanek commented 4 years ago

Version taken from contents of file: 2019-12-30_13-38

alexandreborges commented 4 years ago

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.

image

mkilijanek commented 4 years ago

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:

  1. Create directory for malwoverview.
  2. Make virtualenv in directory from previous step.
  3. source {malwoverview_dir}/bin/activate
  4. cd {malwoverview_dir}
  5. pip install malwoverview
  6. cd bin
  7. Edit configmalw.py providing all API keys (I used literally all variables)
  8. ./malwoverview
  9. Observe if your API keys are recognized.

I think result might differ between Linux distros :(

mkilijanek commented 4 years ago

Config file location is in bin directory of Virtualenv. No directory structure as you described is observed.

alexandreborges commented 4 years ago

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.

image

alexandreborges commented 4 years ago

Due to no further comments, I'm closing the issue.