Awesome; thanks!

On Thursday, March 18, 2010, Yutaka Sato <feedback@delegate.org> wrote:
> Hi,
>
>>>Subject: using delegate to put http authentication on top of a SOCKS proxy connection
>
> To forward connections via a SOCKS server (at socksHost:socksPort)
> with authentication (userName:passWord), add parameters as follows:
>
>   SOCKS="socksHost:socksPort:*" MYAUTH=userName:passWord:socks
>
> Cheers,
> Yutaka
> --
>   9 9   Yutaka Sato <y.sato@delegate.org> http://delegate.org/y..sato/
>  ( ~ )  National Institute of Advanced Industrial Science and Technology
> _<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
> Do the more with the less -- B. Fuller
>
> In message <_A4759@delegate-en.ML_> on 03/15/10(22:12:41)
> you alec resnick <ps4jabdyi-qa4rnudhoza6.ml@delegate.org> wrote:
>  |I have two remote machines, remote1 and remote2. remote2 is only
>  |running sshd, and I can't run anything else on it. remote1 is a
>  |full-fledged server to which I have complete access. I can run a SOCKS
>  |proxy on remote2 via ssh -f -N -D *:8080 me@remote2 which lets me
>  |expose a SOCKS proxy on port 8080 on remote1. I'd like to authenticate
>  |this so that the proxy isn't sitting open. How can I do this?
>  |
>  |It seems like I should be able to use delegate, but I can't even seem
>  |to get its HTTP proxy functionality working. When I run delegated -r
>  |-P8081 SERVER=http PERMIT="*:*:*" REMITTABLE="*" I can't even get it
>  |to work on port 8081. . .it fails either with "not reliable" or bans
>  |my IP as a suspected intruder.
>
>

-- 
alec resnick  /  http://alecresnick.org  /  @aresnick  /  617.229.5036