search

bettercap / caplets

caplets and proxy modules.
Other
484 stars 152 forks source link

http-dump-req caplet doesn't dump nearly anything #12

Closed q2dg closed 6 years ago

q2dg commented 6 years ago

I attach two images, one when using http.proxy and another when using https.proxy. Requests are intercepted (it seems so) but there's nearly no information logged on screen. I've looked at associated Javascript code and, in theory, a lot more data should be shown.

I'm using bettercap 2.4 in Ubuntu 17.10 64 bits, binary downloaded from official releases

With http.proxy: http proxy

With https.proxy: https proxy

buffermet commented 6 years ago

Can you please write a complete issue? We can't help you if you just dump the result here and expect us to figure out what you're doing.

screenshot from 2018-04-09 11-58-08

q2dg commented 6 years ago

Ok. If I enter into interactive console of Bettercap (version 2.4 installed from official binary release in a VirtualBox VM with a Ubuntu Server 17.10 64 bits OS with its enp0s3 interface in "bridged" mode and using systemd-networkd with netplan disabled) and I execute on it these commands (192.168.1.2 is the IP of my real system)...:

set http.proxy.script caplets/http-req-dump.js http.proxy on set arp.spoof.targets 192.168.1.2 arp.spoof on

...when I go to http://www.marca.com from 192.168.1.2 I get first screenshot shown above. If I execute these commands...

set https.proxy.script caplets/http-req-dump.js https.proxy on set arp.spoof.targets 192.168.1.2 arp.spoof on

..when I go to https://www.hola.com from 192.168.1.2 I get second screenshot show above, instead.

Maybe it's an error in VBox network stack, maybe it's fault of my LAN (wifi) router, I don't know...

Well, if nobody else has this error, it's fine if it remains closed. But it's good having it here as a reference for eventual future cases. Thanks

buffermet commented 6 years ago

Is your only problem that the headers are missing? Traffic is being proxied fine?

q2dg commented 6 years ago

Yes!