debian ? about venom HOT 14 CLOSED

funny .. i just downloaded & tried venom v.1.0.12 and its working fine! something wrong here!

BTW..Debian Testing + pywin32 installed and working fine.

from venom.

finally .. after inserting "1º bug-fix" everything worked fine.

from venom.

after choosing option no.4 followed by the option "pyinstaller" i get this:

also, got this at script startup though i`m using metasploit-framework the git version:

again, all are on debian-testing.
thank you.

from venom.

yep ran setup.sh everything was ok & yes ..

wine 32bit is installed & working fine...
also tested pyinstaller & MinGW separately on wine to confirm its working ..

after pyinstaller compiles it doesnt produce .exe file,
it gets removed somehow. can`t figure out whats going wrong.

0.0.0.0 was my last resort to verify all ip types :)

my distro is: Debian Testing

from venom.

i just downloaded & tried venom v.1.0.12 <-- thanks for this report ..

now iam current finishing another project,
but in 2 weeks tops i will return woking in venom new release ..
maybee at that time with your help we can make this work in your distro ..

from venom.

thank you for your time & effort .. will be on a look out for you next proj.

cheers.

from venom.

1 - my script as identified (uname -m) your system as 64 bits ..
2 - so when its going to 'compile' agents, it uses 64bits configurations ..

(I belive thats the reason for this bug now, because 64bits supported was added in v1.0.13)
And you have decided to install all dependencies using wine (32bits) <-- I did not expect this = bug .

quick fix:

a) Edit venom.sh script
b) Change the values from lines 83 to 84 ..

By this ones (32bits)

c) save the script and run it again ..

Final notes:

This configuration will force venom to use 32bits settings when compiling agents ..
Dont forget to report if this soluction has suite you, for me to close this issue ..

from venom.

Debian-testing has stopped using "i586-mingw32msvc-gcc"
instead uses "i686-w64-mingw32-gcc" for 32bit compilation.
also 64bit will be "x86_64-w64-mingw32-gcc".

though ill give it a try & let you know.

from venom.

just tried you suggestion & got an extra negative outcome. though the correct path for PyInstaller was found, it refuses to compile it to .exe plus "cp from /home/USER/$IPATH/output/dist not found or directory non existing!" pops up.

so in short, i`m left with a *.py & *.raw files with no *.exe
very frustrating ... i guess its better to suggest if i may that venom remains a "kali" only framework
rather than entirely manipulating the script to fit debian or ubuntu .. etc.

thx in adv.

from venom.

Dont say its only a KALI thing, because many people with diferent linux distros use it ..
ubuntu, kali, parrot, mint <-- venom was tested in this distros (team menbers)

Lets try this last soluction:

lets look at venom command that compiles the agent...

1 - check if the bash variable user= its storing correctlly your username
The command it can be found in line 46

2 - maybee its su $user -c thats giving the error under your distro ..
3 - also check if the paths to python26 and pyinstaller-2.0 are correct ..
The command it can be found in line 1214

HINT: maybee the error its on pyinstaller.3.2.1 install path because my tool search's for pyinstaller-2.0 ..

Final notes:

Ive been reading the diference from venom v1.0.12 to v1.0.13

1 - in v1.0.12 this lines are not present (arch check)

2 - this is the pyinstaller command present in v1.0.12

P.S: did you installed pywin32 and pyinstaller as root user ?**
does WINE in your distro its owned by username or by root ?

from venom.

Installed pywin32 and pyinstaller as user.
Wine owned by user.
Using PyInstaller-3.2.1 --> path is at /opt/.

Plus, tried removing the "su $user -c" part & no luck.
any hints or do you know anyone running the script on debian?

note: in v1.0.12 i tweaked pyinstaller like this:
"wine ~/.wine/drive_c/Python27/python.exe /opt/PyInstaller-3.2.1/pyinstaller.py --noconsole --onefile $IPATH .....etc"

also python27 is installed.

from venom.

1- if your wine its owned by username ..
Then su $user -c its needed ...

because venom its beeing executed as root user ..
and wine its owned by username ..

2 - check if user= bash variable stores the correct value (your username)..

user=`who | cut -d' ' -f1 | sort | uniq`

If not.. then change the value to this:

3 - the problem its on python26 and pyinstaller-2.0 install paths too ..
Then tweak v1.0.13 to use that configuration too ..

"$arch ~/.wine/drive_c/Python27/python.exe /opt/PyInstaller-3.2.1/pyinstaller.py --noconsole --onefile $IPATH .....etc"

4 - check if this value its correct too ..

HINT: $DrIvC == /root/.wine/drive_c (in settings file)

5 - Dont forget to change the wine64 value to wine

6 - replace string '/etc/init.d/metasploit' in main script using SED bash command:

a) cd venom-main
b) sed -i "s|/etc/init.d/metasploit|service metasploit|g" venom.sh
c) run script again ( this should fix the msf service {start|stop} )..

This should do the trick ..

from venom.

Note:

If the installation process informs you that Python is not found in the registry,
it almost certainly means you have downloaded the wrong version
either for the wrong version of Python, or the wrong "bittedness".
https://sourceforge.net/projects/pywin32/files/pywin32/Build%20220/

1º bug-fix

venom v1.0.14 allows users to manually install another versions
of this 2 softwares and use the 'settings' file to force main tool to use them ..

2º bug-fix

template.py execution under windows systems fixed with the insertion of new windows API imports

from venom.

iam sorry about that ..
but i was busy in other projects 👍
many thanks for your bug-report and help me understanding were the bug is under your distro ..

this new version will be released in day 30 maybee ..
check here the changelog: https://github.com/r00t-3xp10it/venom/blob/master/bin/changelog.ve

from venom.