Re: FW: Questions on Polipo capabilities and potential capabilities

privacy-ecosystem.com WebMaster wrote:
> (1) How would you suggest we have polipo automatically shut down after 60 or
> x minutes?  Could support be added to allow having it shutdown automatically
> x minutes after it started up?

I'm guessing this isn't Polipo's job. Use something like cron to start
and shutdown polipo.

> (2) In a similar vein, could polipo be made to support the kind of
> "accounting" functionality that exists in Tor?  Have it automatically start
> up and shut down after x MB/GB of traffic has flowed through it each day?
> Have it automatically start up at the same time each day?

Automatically start up at the same time each day is another job for
cron. The rest of it, I'm not sure about -- there are traffic shaping
systems, but I don't think that's quite what you want.

> (3) Can polipo recognize and "zap" any Javascript scripts?  Alternatively,
> can it be made to call out to an external script like it does with adzapper
> to process/scrub any Javascript scripts?

I would assume that if adzapper does what I think it does, a similar
thing could be done with Javascript. I don't know exactly what program
you'd run, though.

Is there a reason you can't just have JavaScript disabled on the clients?

> (5) Have you any experience with OpenVPN?

I do.

I don't know if you can make https go through Polipo. I would suggest,
though, that it might be easier to connect to Polipo with https, even
for normal http traffic. I don't know if Polipo supports this natively,
but you could try something like stunnel or apache+mod_ssl+mod_proxy in
front of Polipo.

> I am trying to get a local
> OpenVPN client configuration to send all internet protocols/traffic through
> to the OpenVPN server process, which then routes http, https and ftp through
> polipo.  No luck at this point...

First of all, I don't think Polipo handles FTP, and I doubt it ever will.

But more relevantly, the reason I mentioned doing https instead of
OpenVPN is that ultimately, OpenVPN will require the exact same
configuration here. The only advantage of OpenVPN is if you find it
easier to manage keys with it than with SSL, but you still have to tell
your web browser to connect to the VPN server's IP.

You might be tempted to set the VPN as the default gateway. I don't
think this actually works -- remember, default gateway is how it knows
how to connect to the VPN server in the first place.

You might set up some clever firewall rules on the client-side, using
DNAT, to force all http traffic through the proxy server. If this is
what you're doing, then you need the VPN, but I'm pretty sure it won't
work for https, and it's also tricky, nonstandard, and probably not
supported by Polipo. Squid will do it, but just for HTTP, and really, if
you have the luxury of configuring a VPN and a firewall on the client,
it makes much more sense to block all outbound HTTP and HTTPS except
that which goes through the proxy, and then configure your clients to
actually know about the proxy.

It would help if we knew what you were trying to accomplish.

signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
Polipo-users mailing list
Polipo-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/polipo-users