Re: [squid-users] Sock Proxy Traffic

Thanks, it works No more error in the log.
Regards,
Yomi.

> Do not configure the HTTPSProxy, only the HTTPProxy, and see if that
> works. Squid does everything across the same port.
>
>>>> <squid_at_sourcesystemsonline.com> 3/2/2011 11:23 AM >>>
> Thank you for your swift response.I have done all you suggested but it
> still gives error:"ket. 02 17:01:24.897 [Warning] The https proxy sent
> back an unexpected status code 403 ("Forbidden"). Closing." when i
> configure Tor to use squid proxy, why?
>
> VidaliaLog-03.02.2011.txt
>
> ket. 02 17:00:37.665 [Notice] Tor v0.2.1.29 (r8e9b25e6c7a2e70c). This
> is
> experimental software. Do not rely on it for strong anonymity. (Running
> on
> Windows "Longhorn" Service Pack 2 [workstation] {personal} {terminal
> services, single user})
> ket. 02 17:00:37.774 [Notice] Initialized libevent version
> 1.4.14-stable
> using method win32. Good.
> ket. 02 17:00:37.774 [Notice] Opening Socks listener on 127.0.0.1:9050
> ket. 02 17:00:37.774 [Notice] Opening Control listener on
> 127.0.0.1:9051
> ket. 02 17:00:37.774 [Notice] Parsing GEOIP file.
> ket. 02 17:00:48.267 [Notice] OpenSSL OpenSSL 0.9.8p 16 Nov 2010 looks
> like version 0.9.8m or later; I will try SSL_OP to enable
> renegotiation
> ket. 02 17:00:48.267 [Notice] We now have enough directory information
> to
> build circuits.
> ket. 02 17:00:48.268 [Notice] Bootstrapped 80%: Connecting to the Tor
> network.
> ket. 02 17:00:48.268 [Notice] Bootstrapped 85%: Finishing handshake
> with
> first hop.
> ket. 02 17:00:48.268 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:00:48.268 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:00:48.915 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:00:49.896 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:00:50.877 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:23.865 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:24.897 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:25.864 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:26.866 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:27.873 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:28.905 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:30.883 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:31.904 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:32.889 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:33.988 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:34.861 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:35.936 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:36.898 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:38.897 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:01:39.936 [Warning] The https proxy sent back an unexpected
> status code 403 ("Forbidden"). Closing.
> ket. 02 17:02:02.372 [Notice] Bootstrapped 90%: Establishing a Tor
> circuit.
> ket. 02 17:02:21.473 [Notice] Tor has successfully opened a circuit.
> Looks
> like client functionality is working.
> ket. 02 17:02:21.473 [Notice] Bootstrapped 100%: Done.
>
> Tor Config File
>
> # This file was generated by Tor; if you edit it, comments will not be
> preserved
> # The old torrc file was renamed to torrc.orig.1 or similar, and Tor
> will
> ignore it
>
> # If set, Tor will accept connections from the same machine (localhost
> only)
> # on this port, and allow those connections to control the Tor process
> using
> # the Tor Control Protocol (described in control-spec.txt).
> ControlPort 9051
> HashedControlPassword
> 16:B84A6BA23097A2CD60EF438BD0B2C209E01054D6F95D58F02EAA00963C
> # Force Tor to make all HTTP directory requests through this host:port
> (or
> # host:80 if port is not set).
> HttpProxy 192.168.137.1:3128
> # Force Tor to make all TLS (SSL) connections through this host:port
> (or
> # host:80 if port is not set).
> HttpsProxy 192.168.137.1:3128
> # Where to send logging messages. Format is minSeverity[-maxSeverity]
> # (stderr|stdout|syslog|file FILENAME).
> Log notice stdout
> # Bind to this address to listen to connections from SOCKS-speaking
> # applications.
> SocksListenAddress 127.0.0.1
> Regards,
> Yomi
>
>
>
>> Please read the configuration Manual for the said software on:
>> https://www.torproject.org/docs/tor-manual.html.en
>>
>> In there, you will find different configuration parameters for
>> utilizing proxies:
>>
>> HTTPProxy host[:port]
>> Tor will make all its directory requests through this host:port
> (or
>> host:80 if port is not specified), rather than connecting directly
> to
>> any directory servers.
>>
>> HTTPProxyAuthenticator username:password
>> If defined, Tor will use this username:password for Basic HTTP
>> proxy authentication, as in RFC 2617. This is currently the only form
> of
>> HTTP proxy authentication that Tor supports; feel free to submit a
> patch
>> if you want it to support others.
>>
>> HTTPSProxy host[:port]
>> Tor will make all its OR (SSL) connections through this
> host:port
>> (or host:443 if port is not specified), via HTTP CONNECT rather than
>> connecting directly to servers. You may want to set FascistFirewall
> to
>> restrict the set of ports you might try to connect to, if your HTTPS
>> proxy only allows connecting to certain ports.
>>
>> HTTPSProxyAuthenticator username:password
>> If defined, Tor will use this username:password for Basic HTTPS
>> proxy authentication, as in RFC 2617. This is currently the only form
> of
>> HTTPS proxy authentication that Tor supports; feel free to submit a
>> patch if you want it to support others.
>>
>> Socks4Proxy host[:port]
>> Tor will make all OR connections through the SOCKS 4 proxy at
>> host:port (or host:1080 if port is not specified).
>>
>> Socks5Proxy host[:port]
>> Tor will make all OR connections through the SOCKS 5 proxy at
>> host:port (or host:1080 if port is not specified).
>>
>> Socks5ProxyUsername username
>> Socks5ProxyPassword password
>> If defined, authenticate to the SOCKS 5 server using username
> and
>> password in accordance to RFC 1929. Both username and password must
> be
>> between 1 and 255 characters.
>>
>>
>>>>> <squid_at_sourcesystemsonline.com> 3/2/2011 9:27 AM >>>
>> Hi,
>> I am using squid2.7STABLE8 on Windows 7 Ultimate.
>> I very aware that squid is a http proxy and cache program but am
> using
>> sock program - Tor anonymity program from torproject.org and i will
>> like
>> the sock traffic to pass through squid so that it can be cache.
>> Is it possible and how?
>> Yomi.
>>
>>
>> Travel Impressions made the following annotations
>> -------------------------------------------------------------
>> "This message and any attachments are solely for the intended
> recipient
>> and may contain confidential or privileged information. If you are
> not
>> the intended recipient, any disclosure, copying, use, or distribution
> of
>> the information included in this message and any attachments is
>> prohibited. If you have received this communication in error,
> please
>> notify us by reply e-mail and immediately and permanently delete
> this
>> message and any attachments.
>> Thank you."
>>
>
>
>
> Travel Impressions made the following annotations
> -------------------------------------------------------------
> "This message and any attachments are solely for the intended recipient
> and may contain confidential or privileged information. If you are not
> the intended recipient, any disclosure, copying, use, or distribution of
> the information included in this message and any attachments is
> prohibited. If you have received this communication in error, please
> notify us by reply e-mail and immediately and permanently delete this
> message and any attachments.
> Thank you."
>
Received on Wed Mar 02 2011 - 16:34:05 MST