Re: [squid-users] Securing squid3

2013-02-15 Thread Andreas Westvik
Oh, this was a lot of information! :D So here goes. Im only using squeeze on the production server. On the testing server Im running wheezy, but not squid. Only havp. And yeah, I seems a bit poor but I was only testing this as proof of concept. Or to satisfy my inner nerd. Im not going to use

Re: [squid-users] Securing squid3

2013-02-14 Thread Amos Jeffries
On 15/02/2013 10:18 a.m., Andreas Westvik wrote: So i actually got it working! Client -> gateway -> havp -> squid -> internets I actually had blocked my self totally from squid3, so that was quite the head scratch. It turned out that http access deny all has to be at the bottom of the config f

Re: [squid-users] Securing squid3

2013-02-14 Thread Andreas Westvik
So i actually got it working! Client -> gateway -> havp -> squid -> internets I actually had blocked my self totally from squid3, so that was quite the head scratch. It turned out that http access deny all has to be at the bottom of the config file. ;) So then I pasted this into squid.conf c

Re: [squid-users] Securing squid3

2013-02-14 Thread Andreas Westvik
heh, try this one http://bildr.no/view/1389674 On Feb 14, 2013, at 16:49 , Andreas Westvik wrote: > Sorry, I have been replying directly to users email. > > To clear things up, here is a image of the setup: > > http://bildr.no/image/1389674.jpeg > > > havp is running on 192.168.0.24:3127

Re: [squid-users] Securing squid3

2013-02-14 Thread Andreas Westvik
Sorry, I have been replying directly to users email. To clear things up, here is a image of the setup: http://bildr.no/image/1389674.jpeg havp is running on 192.168.0.24:3127 squid3 is running on 192.168.0.1:3128 -Andras On Feb 14, 2013, at 16:45 , babajaga wrote: > I think, 2 corrections:

Re: AW: [squid-users] Securing squid3

2013-02-14 Thread babajaga
I think, 2 corrections: Instead >squid.conf: cache_peer localhost parent 8899 0 no-query no-digest < squid.conf: cache_peer avp-host parent 8899 0 no-query no-digest never_direct allow all Otherwise, uncachable requests will not go thru parent proxy, but direct. Which will result in some fil

WG: [squid-users] Securing squid3

2013-02-14 Thread Fuhrmann, Marcel
squid/ -Ursprüngliche Nachricht- Von: Andreas Westvik [mailto:andr...@spbk.no] Gesendet: Donnerstag, 14. Februar 2013 16:29 An: Fuhrmann, Marcel Betreff: Re: [squid-users] Securing squid3 Thanks for the answers! Went from: tcp0 0 *

AW: [squid-users] Securing squid3

2013-02-14 Thread Fuhrmann, Marcel
: Andreas Westvik [mailto:andr...@spbk.no] Gesendet: Donnerstag, 14. Februar 2013 15:43 An: squid-users Betreff: [squid-users] Securing squid3 Hi everybody I have been running squid3 on my Debian squeeze on/off for a few weeks now. And there is a few things Im not sure of 1. How can I be sure that

[squid-users] Securing squid3

2013-02-14 Thread Andreas Westvik
Hi everybody I have been running squid3 on my Debian squeeze on/off for a few weeks now. And there is a few things Im not sure of 1. How can I be sure that Im running it securely? I really only want squid3 to server my local clients (192.168.0.0/32). 2. Can I bind squid3 to only listen to any