Re: [proxyTools-users] escaping a very restrictive

[Michael F. <Mic...@tb...>]

> [..]
> >
> > Checking proxy capabilities ...
> > send() on closed socket PROXY at statProxy.pl line 1016.
> > Your vendor has not defined POSIX macro EWOULDBLOCK, used at statProxy.pl line
> > 1
> > 017
>
> This bug has been fixed. Get a new statProxy.pl
>

New version got - localproxy, localproxy2, statproxy, findproxy and the new cgi
stuff.

master.pl returns the same result as last time - all ports `blocked` except 25 and
110 which are `open`. Its possible that is partly to allow us to use yahoo messenger
- annoying as I can`t actually get that to work - lol :-)

C:\Program Files\localproxy>perl statproxy.pl -t 0 -a ,192.168.0.1:8080,******,
****** 192.168.0.1:8080
Subroutine blocking redefined at statproxy.pl line 82.

statProxy v4.104 report from 192.168.4.67:
192.168.0.1     :8080  T                    ?/?


C:\Program Files\localproxy>

This was an interesting one !!

Localproxy now functions ok, picks up the right authentication details from the
environment variables but still can`t find a way out. Haven`t played with it much
yet though.... haven`t looked at the cgi options yet but was intruiged  by this -
have I used the right parameters ?

Mike