Thanatopsis <Thanatopsis@Aegean.Sea> wrote:

> Anyone know of a way to stop Privoxy leaking _actual_ Firefox user-agent info when
> connecting HTTPS (SSL)?

That's impossible. Privoxy isn't "leaking" anything, the information is
encrypted before it ever reaches Privoxy. If Privoxy could successfully
modify anything in an HTTPS stream it would mean SSL was completely
broken.

One could, I suppose, use something like stunnel to move the SSL
negotation a littler further out on the chain and still modify HTTP
headers for SSL-enabled connections before they left your machine.
I'd suspect this would be a little "clunky" to say the least. You'd
essentially have to set up a new tunnel for every connection, and limit
your browser to one, at that site alone. Maybe something like JanusVM
or some other gateway would be better suited to the task...??

In any case you'd absolutely have to fool your browser into thinking it
was making a "standard" connection to an SSL site, and get Privoxy
inserted in there before the data was encrypted.