When activated Subterfuge redirects incoming http traffic to itself on port
10000 for SSLStriping. This prevents collaborative systems from accessing
Subterfuge when it is served on port 80. A fix is incoming; in the interim
serve up Subterfuge using a port other then 80 during collaborative exercises.
Original issue reported on code.google.com by Mtoussain@gmail.com on 23 Nov 2013 at 8:50
Original issue reported on code.google.com by
Mtoussain@gmail.com
on 23 Nov 2013 at 8:50