Notices

Originally Posted by vi_

http://pastebin.com/rmvNSCAR

latest dev version.

This does not need xterm or bash to be installed. Install as per unhumans instructions in post #1. Except miss out xterm and bash.

All processes are shut down nicely

only problem I see with limited testing is the ettercap window doesnt close (after it has been killed). A solution is in the works.

Originally Posted by torpedo48

Testing right now, seems to work pretty well. Just a doubt: how should I launch it? If I launch it with bash ("bash mitm.etc.sh") no problems at all, but that would include bash as a dependency, wouldn't that?

If I make it executable and launch it without bash (just "./mitm.etc.sh"), it SegFaults (invalid -n option in final function, so the menu goes crazy).

Insults are welcome if this is a dumb question

Originally Posted by vi_

Well thats odd, it starts fine on my one. You need to download the script, chmod +x it (make executable) then run it (i.e. while in the same directory as script type ./<the name of the script>)

Please tell me:

Are you using busybox power? To test, type busybox from the xterm and tell me your version number.

The -n flag on the read command isnt really needed, I just liked not having to press return after each choice.

If you are using the stock busybox then we will have to remove the '-n 1' from all the instances of the 'read' command. It is no great loss really.

As for ettercap not shutting down, this is a good thing. Ettercap PREFERS to have you quit properly with 'q' button so it can un-ARP everyone (shutdown nicely). With this in mind I am thinking of removing the instances of killall ettercap, forcing the user to shut it down properly. That is of course unless someone can work out how to send a 'q' keystroke to the ettercap window. However I feel that is a stick of dynamite to crack a nut.

If all this is the case, then all we need to do is remove the wgets, correct some spelling, slap its *** and send it on its way!

tl;dr, stock busybox might not like -n 1 parameter. Please report your version of busybox.

Originally Posted by torpedo48

I was launching it the right way, but as you correctly said I was not using busybox power (busybox version was the stock one, 1.10.2): just installed it, now it works flawlessly. We should add busybox-power as a dependency, or remove the -n 1 parameter (better).

BTW I can't properly use the script without changing the temp folder: ettercap always stops its activity when the log file exceeds ~930 KB (because /tmp is full). Shouldn't we change the temp folder too?

Originally Posted by vi_

Now your cookin' with gas bro! The obvious solution is to remove ALL instances of '-n 1' (fewer dependancies woot!)

Very good point with the moving of the temp folder, we want to minimise read/writes on the NAND (and <1MB is too small). The obvious place is somwhere in /opt. If there is an '/opt/tmp', put it there. If there is not, we will create one.

So:

1. remove all instances of '-n 1'
2. check/create for /opt/tmp
3. possibly check if script is being run as root and exit if not.
4. edit some of the wordage for better flow.
5. remove the wgets.

Originally Posted by torpedo48

This is my last version of the script:

http://pastebin.com/YGjb7UeE

It should create /opt/tmp and operate there, however it still saves the results in /root. I'd like to make it saving the output somewhere else, e.g. /opt/yamas or/MyDocs/Yamas or even MyDocs/.documents/yamas for more user-friendliness; what do you think about it?