Hi,
I have tested squid reverse proxy mode and squid SSL bump both were
successful and working fine.
Is it possible to configure a squid reverse proxy with SSL-bump enabled?
I tried configuring a squid instance in reverse proxy to bump specific
domain traffic using following config line(clubbing
Thx for reply, Alex
%ts works both in REQMOD and RESPMOD, %>a is OK too.
So it seems that %:
> On 09/07/2015 10:08 PM, Hsuan Yu wrote:
>
> > I didn't see relevant icap config options in squid.conf to carry
> > X-Server-IP in ICAP header
>
> Squid currently has built-in support for X-Client-IP, n
Hello all
I’ve been testing out an SSL bumping config using 3.5.8 for the last week or so
and am scratching my head over a couple of things.
First, here’s my config (shout out to James Lay):
acl tcp_level at_step SslBump1
acl client_hello_peeked at_step SslBump2
acl bump_bypass_domains ssl::ser
On 09/07/2015 10:08 PM, Hsuan Yu wrote:
> I didn't see relevant icap config options in squid.conf to carry
> X-Server-IP in ICAP header
Squid currently has built-in support for X-Client-IP, not X-Server-IP.
> So I tried to use adaptation_meta X-Server-IP: "% 3.5.8/squid 4.x
>
> but not working
Amos
Got the build working finally and the cxx Maxtcp flag shows in my -v but
still getting the 128 port limit!
What a let down Thought I had it for a moment.
On Monday, September 7, 2015, Amos Jeffries wrote:
> On 8/09/2015 2:11 p.m., Jason Enzer wrote:
> > trying to build in larger maxtc
Hello Everyone,
I didn't see relevant icap config options in squid.conf to carry
X-Server-IP in ICAP header
So I tried to use adaptation_meta X-Server-IP: "%SwapChecksum24::raw[0]’
StoreSwapLogData.cc:47:23: note: candidate is:
In file included from StoreSwapLogData.cc:12:0:
StoreSwapLogData.h:70
On 8/09/2015 2:11 p.m., Jason Enzer wrote:
> trying to build in larger maxtcplistenports into 3.5.7 for centos 6
>
> what would i need out of here to get a build working? i mean like it
> does from elizers repo?
You need to find out what is replacing your custon CXXFLAGS setting. I
suspect someth
trying to build in larger maxtcplistenports into 3.5.7 for centos 6
what would i need out of here to get a build working? i mean like it
does from elizers repo?
./configure --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu
--program-prefix= --prefix=/
On 8/09/2015 10:10 a.m., Eliezer Croitoru wrote:
> Hey Howard,
>
> I forgot to mention that squid uses the directory "/var/run/squid" as
> the IPC directory which should be owned by the proxy or squid
> user(depends on the OS).
> From what you have mentioned squid tries to access some directory an
On 8/09/2015 6:32 a.m., Howard Waterfall wrote:
> Rafael / Amos -
> I got my system up and running yesterday. Thanks so much for the help. I
> couldn't get some of the suggestions that Amos made to work, but they did
> after running some of the commands on Rafael's wiki, so a real team effort!
>
>
On 8/09/2015 9:57 a.m., Howard Waterfall wrote:
> Thanks Eliezer.
>
> Looking at my notes, I'm pretty sure that:
>
> *apt-get build-dep squid*
>
> was a typo and I actually did
>
> *apt-get build-dep squid3*
>
> Is there something in the output I provided that confirms it's actually
> squid an
Published at: http://www1.ngtech.co.il/wpe/?p=142
I am happy to release the new RPMs of squid 3.5.8 for Centos 6 64bit,
32bit and CentOS 7 64bit.
The new release includes couple bug fixes and improvements.
The details about the the RPMs repository are at
squid-wiki[http://wiki.squid-cache.o
Hey Howard,
I forgot to mention that squid uses the directory "/var/run/squid" as
the IPC directory which should be owned by the proxy or squid
user(depends on the OS).
From what you have mentioned squid tries to access some directory and
is getting denied by permissions.
Please Don't run squi
Thanks Eliezer.
Looking at my notes, I'm pretty sure that:
*apt-get build-dep squid*
was a typo and I actually did
*apt-get build-dep squid3*
Is there something in the output I provided that confirms it's actually
squid and not squid3? It built OK...
I enabled deb-src because when I did:
*a
Hey Howard,
On 07/09/2015 21:32, Howard Waterfall wrote:
1) Earlier in the thread, Amos suggested I run:
apt-get build-dep squid
You would need to use the "squid3" and not "squid" since this is the
package ubuntu builds squid for.
so the command should be:
apt-get build-dep squid3
I have s
Rafael / Amos -
I got my system up and running yesterday. Thanks so much for the help. I
couldn't get some of the suggestions that Amos made to work, but they did
after running some of the commands on Rafael's wiki, so a real team effort!
After getting it up and running, I found that mac address f
On 8/09/2015 2:32 a.m., Tarot Apprentice wrote:
> Upgraded to Stretch. As you suspected it got confused with which squid, had
> to remove squid3 and install Squid.
>
> Apart from changed all the directories from squid3 to squid and my squid.conf
> it's up and running.
>
> When squid4 comes out
On 8/09/2015 1:17 a.m., Emmanuel Garette wrote:
> Le 07/09/2015 14:01, Amos Jeffries a écrit :
>> On 7/09/2015 10:23 p.m., Emmanuel Garette wrote:
>>> ntlmssp: bad ascii: fffb
>>> ntlmssp: bad ascii: ff99
>>> ntlmssp: bad ascii: ffdc
>>> ntlmssp: bad ascii: fff3
>>> ntlmssp: bad asc
Upgraded to Stretch. As you suspected it got confused with which squid, had to
remove squid3 and install Squid.
Apart from changed all the directories from squid3 to squid and my squid.conf
it's up and running.
When squid4 comes out are they going to keep it as squid or will there be a
squid4
Le 07/09/2015 14:01, Amos Jeffries a écrit :
> On 7/09/2015 10:23 p.m., Emmanuel Garette wrote:
>> ntlmssp: bad ascii: fffb
>> ntlmssp: bad ascii: ff99
>> ntlmssp: bad ascii: ffdc
>> ntlmssp: bad ascii: fff3
>> ntlmssp: bad ascii:
>> ntlmssp: bad ascii: ffdd
>> ntlmssp: bad
On 7/09/2015 10:23 p.m., Emmanuel Garette wrote:
>
> ntlmssp: bad ascii: fffb
> ntlmssp: bad ascii: ff99
> ntlmssp: bad ascii: ffdc
> ntlmssp: bad ascii: fff3
> ntlmssp: bad ascii:
> ntlmssp: bad ascii: ffdd
> ntlmssp: bad ascii: fffa
> ntlmssp: bad ascii: ff8f
> nt
Le 07/09/2015 12:00, Amos Jeffries a écrit :
> On 7/09/2015 8:01 p.m., Emmanuel Garette wrote:
>> Hi,
>>
>> I manage to migrate my squid version from 3.1.19 to 3.3.8 (version
>> included in ubuntu LTS) and I'm using the helper ntlm_smb_lm_auth helper.
> Please make an effort not to use this helper.
On 7/09/2015 8:01 p.m., Emmanuel Garette wrote:
> Hi,
>
> I manage to migrate my squid version from 3.1.19 to 3.3.8 (version
> included in ubuntu LTS) and I'm using the helper ntlm_smb_lm_auth helper.
Please make an effort not to use this helper. It is well worth avoidng
if you can. Your network
Hi,
I manage to migrate my squid version from 3.1.19 to 3.3.8 (version
included in ubuntu LTS) and I'm using the helper ntlm_smb_lm_auth helper.
I cannot authentifiate any user with this version of the helper.
I've two problem:
* in file lib/ntlmauth/ntlmauth.cc, this line is not working:
runninng
./configure CXXFLAGS="-DMAXTCPLISTENPORTS=200" when i make install
squid is not showing me the increased listen ports.
squid -v shows
Squid Cache: Version 3.5.7
Service Name: squid
configure options: '--build=x86_64-redhat-linux-gnu'
'--host=x86_64-redhat-linux-gnu' '--target=x86_64-re
25 matches
Mail list logo
