Harvester/Tabnabbing methods only work on port 80? about social-engineer-toolkit

[L1ghtn1ng]

Try setting port forwarding on your router and see if that does the trick

On 13 Apr 2014 03:52, lucio-cengage [email protected] wrote:
I'm trying perform the Harvester/Tabnabbing methods from SET outside my local network. So since my ISP blocks the port 80 I changed the parameter WEB_PORT on set_config to another port (e.g 3505). After that I executed the Harvester/Tabnabbing and sent my external IP with the port to a friend, the site loaded normally on his PC and I got the hits on my terminal. However, when my friend clicks on button to send the data I have not received answer and the site on his browser gave fault to loading the page. Seems the cloned site try to answer in port 80 and not on the same port that I had changed. So, Is there any way that I can fix it? Thank you.

---

Reply to this email directly or view it on GitHub:
#64

[lucio-cengage]

The port forwarding was already setted on my router when I tested and it's working. To load the site on my friend's PC the port change is working but to receive the data wrote by him don't. And I had to change the port because my ISP blocks the port 80.

[L1ghtn1ng]

Then it might be a bug within set but could be a problem related to how your ISP is routing traffic, lets see what Dave has to say on this. But have you tried doing a packet capture to see if that sheds light on the problem in the mean time to help get a better idea of the issue?

On 13 Apr 2014 04:23, lucio-cengage [email protected] wrote:
The port forwarding was already setted on my router when I tested and it's working. I think the problem is when my friend clicks to send the data from me the cloned site try to answer in port 80 and not on the port that I changed on set_config. To load the site on my friend's PC the port change is working but to receive the data wrote by him don't. And I had to change the port because my ISP blocks the port 80.

---

Reply to this email directly or view it on GitHub:
#64 (comment)

There's two methods to accomplish this, the first is through specifying APACHE_SERVER=ON in the config/set_config directory, then configure Apache to go to any port you want to under /etc/apache2/.

You can also edit the config/set_config and change WEB_PORT=80 to whatever port you want to run the harvester/tabnabbing on.

[lucio-cengage]

I've tried both methods but neither of them worked. In both situations the same thing happens: the cloned site loads in the others PCs outside my local area network, but when the button to sent the information written in the form fields is clicked nothing happens neither in my terminal nor the other computers.

It seems that even with the port change in the set_config the cloned site tries to answer in default port (port 80), and thus nothing happens because the server is not listening on this port anymore.

[L1ghtn1ng]

The only thing I can think of is set a redirect rule on your router for anything that tries to connect on 80 gets redirected to your desired port

On 14 Apr 2014 19:35, lucio-cengage [email protected] wrote:
I've tried both methods but neither of them worked. In both situations the same thing happens: the cloned site loads in the others PCs outside my local area network, but when the button to sent the information written in the form fields is clicked nothing happens neither in my terminal nor the other computers.

It seems that even with the port change in the set_config the cloned site tries to answer in default port (port 80), and thus nothing happens because the server is not listening on this port anymore.

---

Reply to this email directly or view it on GitHub:
#64 (comment)

[lucio-cengage]

That's the problem L1ghtn1ng, my router does not receive any connection on port 80 because this port like other (e.g. 22, 443...) are blocked by my ISP and this blocks happens on the ISP, therefore it happens before the connection reach my router.

[L1ghtn1ng]

Have you tried changing your DNS from your ISP one to Google's on your router to see if they are blocking it via DNS? If that does not work then I am all out of ideas, seems that you have a unique setup. Will have to see what Dave says

On 15 Apr 2014 00:17, lucio-cengage [email protected] wrote:
That's the problem L1ghtn1ng, my router does not receive any connection on port 80 because this port like other (e.g. 22, 443...) are blocked by my ISP and this blocks happens on the ISP, therefore it happens before the connection reach my router.

---

Reply to this email directly or view it on GitHub:
#64 (comment)

[lucio-cengage]

I changed the DNS from my router to Google's one, but yet I didn't get any connections on port 80 or others that are blocked by my ISP. Thanks for trying help me L1ghtn1ng.

[L1ghtn1ng]

You are most welcome

On 16 Apr 2014 00:57, lucio-cengage [email protected] wrote:
I changed the DNS from my router to Google's one, but yet I didn't get any connections on port 80 or others that are blocked by my ISP. Thanks for trying help me L1ghtn1ng.

---

Reply to this email directly or view it on GitHub:
#64 (comment)