moxie0/sslstrip

Pages at victim does not load at first time

ostrolucky opened this issue · 4 comments

Hi, guys at BackTrack forums pointed out that since sslstrip 0.9 there is present bug which causes that pages sometimes does not load at first try. It throws different errors in different browsers:
Opera: Blank page with text "Location: ht"
Chrome: Classic error "This webpage is not available" with error "Error 321 (net::ERR_INVALID_CHUNKED_ENCODING): Unknown error."
Firefox: It does not react at first time or load blank page

It always loads after refresh.

I can't reproduce this, so a reproducible test case would be great.

I have found a way to reproduce this issue:

Steps:

  1. Use the -k option to kill in progress sessions.
  2. Visit a page where the response headers have a Transfer-Encoding of chunked (http://www.google.com should do it). I would also guess that browser cache has to be cleared.

The errors noted in the above issue will occur. I'm currently using the code in the master branch of the github repo.

koto commented

Chunked encoding is not needed to trigger the error. I can reproduce the error with trying to fetch the http://www.google.com/robots.txt . It does work when '-k' is not used, but displays 'Location: ht' in Opera when '-k' is used:

$ python sslstrip.py -f -a -k

Log file:
2012-02-01 17:56:26,109 Reading tamper config file: False
2012-02-01 17:56:27,826 Resolving host: www.google.com
2012-02-01 17:56:27,826 Host not cached.
2012-02-01 17:56:27,834 Resolved host successfully: www.google.com -> 173.194.69.147
2012-02-01 17:56:27,834 Sending expired cookies...

and it stops there.

It's only for the first request in sslstrip session. Trying to refetch the resource will suceed.

I'm also running into this problem, is there any known fix?

EDIT: I'm using the latest version of Google Chrome in case that helps