|
|
Post by xtr4nge on Aug 8, 2015 9:05:24 GMT
--  |
|
silo
New Member
Posts: 3 
|
Post by silo on Oct 7, 2015 14:45:18 GMT
Using Kali, FW 2.2, start modules nginx, AP, mana, mitmf
mitmf clashes with AP DNS port. Can I change the port of either AP or mitmf
root@kali:/usr/share/mitmf# ./mitmf.py -i wlan0
[DNSChef] Unable to start DNS server on port 53: port already in use
root@kali:/usr/share/mitmf# netstat -an|grep :53
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.1:53 0.0.0.0:* LISTEN
tcp6 0 0 ::1:53 :::* LISTEN
udp 0 0 127.0.0.1:53 0.0.0.0:*
udp 0 0 192.168.0.1:53 0.0.0.0:*
udp6 0 0 ::1:53 :::*
|
|
|
|
Post by xtr4nge on Oct 9, 2015 12:25:35 GMT
Hi Silo,
Did you run the file install.sh? (manually or from the web-interface is the same)
/usr/share/fruitywifi/www/modules/mitmf/includes/install.sh
if you check the content of the file, you will see the patch that changes the DNS port on MITMf.
regards,
|
|
silo
New Member
Posts: 3
|
Post by silo on Oct 12, 2015 0:06:59 GMT
Hi,
The web-interface says it's installed. Running it manually installs a whole load of dependencies, I also installed python-setuptools and pip to get the script working. The end result is the same error message:
[DNSChef] Unable to start DNS server on port 53: port already in use
|
|
|
|
Post by mendoza on Oct 14, 2015 11:29:22 GMT
Hi, The web-interface says it's installed. Running it manually installs a whole load of dependencies, I also installed python-setuptools and pip to get the script working. The end result is the same error message: [DNSChef] Unable to start DNS server on port 53: port already in use Hi Silo, You can try kill the proccess that is in 53 port # fuser -k 53/tcp # kill -9 PID (process id number) |
|
|
|
Post by mendoza on Oct 14, 2015 11:40:50 GMT
Hi xtr4nge.
Is there any option in mitmf module where i can add my gateway's network to arpspoof?
I have try with
root@kali:/usr/share/fruitywifi/www/modules/mitmf/includes/MITMf-master# python mitmf.py --spoof --arp --dns --gateway IP -i eth0
and its works great. but i cant find how can i do this in the module fruitywifi webgui
Congrats for your proyects. i love it.
|
|
|
|
Post by xtr4nge on Oct 14, 2015 13:05:23 GMT
Hi, The web-interface says it's installed. Running it manually installs a whole load of dependencies, I also installed python-setuptools and pip to get the script working. The end result is the same error message: [DNSChef] Unable to start DNS server on port 53: port already in use Hi silo, check the config file: /usr/share/fruitywifi/www/modules/mitmf/includes/MITMf-master/config/mitmf.confIn the DNS section you need to have: port = 5300regards, |
|
|
|
Post by xtr4nge on Oct 14, 2015 13:11:29 GMT
Hi mendoza, The option it was not implemented yet in MITMf module for FruityWiFi, but it is very easy to add. If you want to play a little bit with the module to add the option, you can propose a patch on GitHub module page  Thanks a lot regards, |
|
silo
New Member
Posts: 3
|
Post by silo on Oct 14, 2015 21:28:51 GMT
Hi xtr4nge,
Sorry, I should have said that I checked that the install script is correctly patching the config file. I checked the line in /usr/share/fruitywifi/www/modules/mitmf/includes/install.sh which does:
sed -i 's/port.*=.*53.*# Port to listen on/port = 5300 # Port to listen on/' MITMf-master/config/mitmf.conf
and then checked the config file
root@kali:/# cat /usr/share/fruitywifi/www/modules/mitmf/includes/MITMf-master/config/mitmf.conf | grep 5300
port = 5300 # Port to listen on
I also tried mendoza's suggestion and killed the process and it seems to start manually but not in the web-ui. I think I'll try this on a different platform and see if I get the same result.
Thanks,
|
|
bread
New Member
Posts: 3
|
Post by bread on Oct 28, 2015 3:19:24 GMT
Are you planing on making this module connect to byt3bl33d3r's repo so it can stay updated?
|
|
|
|
Post by xtr4nge on Oct 31, 2015 9:30:35 GMT
Hi bread, The reason why I'm not pointing some modules to the original source is because changes introduced by the developers can brake the module, so I prefer to have control on the changes introduced by the developer. I use to do regular updates on the modules but lately I have been working on FruityWiFi API, FruityShell and FruityDisplay. I will update the modules as soon as I can In the meantime, you can always change the installation script and point the source to the original source. If the module breaks, you just need uninstall the module and install it again. For example, for MITMf edit the file: /usr/share/fruitywifi/www/modules/mitmf/includes/install.sh then, exec install.sh from the console. regards, |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 31, 2016 23:29:05 GMT
Hi xtr4nge!
For some reason, MITMf is not working for me. I couldn't even enable the module before, now I have just run install.sh and seen that it couldn't find libpcap.h
So I installed libpcap-dev. That fixed it. Now I can enable MITMf, but it is still not working. None of the modules work and I get a lot of " 16:31:11 [ProxyPlugins] Exception occurred in hooked function" in the output from MITMf.
By running all the scripts in the python shell (and setting the path correctly) I have checked that all the dependencies are correct (they run just fine, they just don't work)
Any ideas?
Thank you very much!
|
|
divjl
New Member
Posts: 1
|
Post by divjl on Aug 9, 2016 16:03:57 GMT
How can I turn on HSTS bypass in MITMf module?
There is a "hsts" checkbox in Options tab, but I didn't notice any difference after checking it.
Also, I can see there are some configurations related to HSTS in Config tab , but I can't turn on SSLStrip+ module (click seems to have no effect).
|
|
|
|
Post by p4tria on Apr 4, 2017 16:26:23 GMT
Hi xtr4nge,
I'm trying to enable mitmf module but it doesn't work...
I've installed fruitywifi in Raspbian with ./intall-FruityWiFi.sh and install-modules.py
AP works ok, but then I try to swich on MITMF and nothing happens... if I go to /usr/share/FruityWifi/modules/mitmf/includes and ./install.sh it seems to install ok
if I do ./mitf says:
ImportError: No module named mitmflib.watchdog.observers
|
|
