Eliezer Croitoru | 13 Jun 2013 01:18
Picon

I was wondering about SSL\socks support from squid side?

I have seen the wiki:
http://wiki.squid-cache.org/Features/Socks

and was wondering about it very much!
I have a situation that I have access to SSL ports only which are being 
detected by NDPI(Deep Inspection) or similar mechanism.
I want to access my local network resources such as files and other data 
on a secure channel that is not:
1. SSH port forwarding\tunneling.
2. VPN
3. Layer 2 secure channels.

I first want to ask for the existing working options that you might know of.
The main issue about it that most of the natted(super multi nantted like 
a government) complex networks doesn't allow the usage of any tunneling 
protocol that can allow network level routing.
Indeed we can always exploit the TCP stack but for this specific it's 
better to use a common proxy protocol that just works.

The situation is a school which has a filtering solution and we want to 
"exploit" in order to give them transparent support.
This school have a lots of sensitive data which we don't want the third 
party which is reliable for filtering but not security to be aware of.

Thanks,
Eliezer

Tsantilas Christos | 11 Jun 2013 12:16
Picon

[PATCH] Deprecate log_icap and log_access configuration directives


The log_icap and log_access are not really needed.
The users have acls control for access and icap logging using the
access_log and icap_log configuration directives.

This patch removes these options from configuration file.

This is a Measurement Factory project
noc | 11 Jun 2013 00:22
Favicon

Build failed in Jenkins: 3.HEAD-amd64-opensuse #522

See <http://build.squid-cache.org/job/3.HEAD-amd64-opensuse/522/>

------------------------------------------
Started by upstream project "3.HEAD-amd64-CentOS-5.3" build number 2464
originally caused by:
 Started by an SCM change
Building remotely on opensuse-x64 in workspace <http://build.squid-cache.org/job/3.HEAD-amd64-opensuse/ws/>
$ bzr revision-info -d <http://build.squid-cache.org/job/3.HEAD-amd64-opensuse/ws/>
info result: bzr revision-info -d <http://build.squid-cache.org/job/3.HEAD-amd64-opensuse/ws/>
returned 0. Command output: "12903 kinkie <at> squid-cache.org-20130609203558-3u1r8742gqjs9tmg
" stderr: ""
[3.HEAD-amd64-opensuse] $ bzr pull --overwrite http://bzr.squid-cache.org/bzr/squid3/trunk/
bzr: ERROR: Connection error: while sending GET /bzr/squid3/trunk: [Errno 110] Connection timed out
ERROR: Failed to pull
Since BZR itself isn't crash safe, we'll clean the workspace so that on the next try we'll do a clean pull...
Retrying after 10 seconds
Cleaning workspace...
$ bzr branch http://bzr.squid-cache.org/bzr/squid3/trunk/ <http://build.squid-cache.org/job/3.HEAD-amd64-opensuse/ws/>
bzr: ERROR: Connection error: while sending POST /bzr/squid3/trunk/.bzr/smart: [Errno 110]
Connection timed out
ERROR: Failed to branch http://bzr.squid-cache.org/bzr/squid3/trunk/
Retrying after 10 seconds
Cleaning workspace...
$ bzr branch http://bzr.squid-cache.org/bzr/squid3/trunk/ <http://build.squid-cache.org/job/3.HEAD-amd64-opensuse/ws/>
bzr: ERROR: Connection error: while sending POST /bzr/squid3/trunk/.bzr/smart: [Errno 110]
Connection timed out
ERROR: Failed to branch http://bzr.squid-cache.org/bzr/squid3/trunk/

noc | 11 Jun 2013 00:24
Favicon

Build failed in Jenkins: 3.HEAD-amd64-FreeBSD-7.2 #1887

See <http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-7.2/1887/>

------------------------------------------
Started by upstream project "3.HEAD-amd64-CentOS-5.3" build number 2464
originally caused by:
 Started by an SCM change
Building remotely on east in workspace <http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-7.2/ws/>
$ bzr revision-info -d <http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-7.2/ws/>
info result: bzr revision-info -d
<http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-7.2/ws/> returned 0. Command output:
"12903 kinkie <at> squid-cache.org-20130609203558-3u1r8742gqjs9tmg
" stderr: ""
[3.HEAD-amd64-FreeBSD-7.2] $ bzr pull --overwrite http://bzr.squid-cache.org/bzr/squid3/trunk/
bzr: ERROR: Connection error: while sending GET /bzr/squid3/trunk: (60, 'Operation timed out')
ERROR: Failed to pull
Since BZR itself isn't crash safe, we'll clean the workspace so that on the next try we'll do a clean pull...
Retrying after 10 seconds
Cleaning workspace...
$ bzr branch http://bzr.squid-cache.org/bzr/squid3/trunk/ <http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-7.2/ws/>
bzr: ERROR: Connection error: while sending POST /bzr/squid3/trunk/.bzr/smart: (60, 'Operation timed out')
ERROR: Failed to branch http://bzr.squid-cache.org/bzr/squid3/trunk/
Retrying after 10 seconds
Cleaning workspace...
$ bzr branch http://bzr.squid-cache.org/bzr/squid3/trunk/ <http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-7.2/ws/>
bzr: ERROR: Connection error: while sending POST /bzr/squid3/trunk/.bzr/smart: (60, 'Operation timed out')
ERROR: Failed to branch http://bzr.squid-cache.org/bzr/squid3/trunk/

Alex Rousskov | 10 Jun 2013 18:00
Favicon

Re: /bzr/squid3/trunk/ r12903: Instruct clang not to treat unused command line arguments as errors

On 06/10/2013 03:27 AM, Amos Jeffries wrote:
> On 10/06/2013 8:35 a.m., Francesco Chemolli wrote:
>> ------------------------------------------------------------
>> revno: 12903
>> committer: Francesco Chemolli <kinkie <at> squid-cache.org>
>> branch nick: trunk
>> timestamp: Sun 2013-06-09 22:35:58 +0200
>> message:
>>    Instruct clang not to treat unused command line arguments as errors
>> modified:
>>    acinclude/compiler-flags.m4
> 
> Anyone known why we have the "-Wno-error=parentheses-equality" option in
> teh first place?
>  It would seem to me to be one of the warnings highlighting a coding
> guideline violation we need to fix in the sources. Not something to be
> suppressed.

I cannot find the description of that clang warning option, but if it
focuses on extra parentheses in benign ((a == b)) cases, then it is a
very minor problem not an important violation. And, as Kinkie pointed
out, if it prevents us from righting (bool a = b), it should stay
disabled even if it finds true problems like (a = b). We can rely on GCC
to spot those true problems.

Cheers,

Alex.

(Continue reading)

Kinkie | 10 Jun 2013 14:59
Picon

Re: /bzr/squid3/trunk/ r12903: Instruct clang not to treat unused command line arguments as errors

On Mon, Jun 10, 2013 at 11:27 AM, Amos Jeffries <squid3 <at> treenet.co.nz> wrote:
> On 10/06/2013 8:35 a.m., Francesco Chemolli wrote:
>>
>> ------------------------------------------------------------
>> revno: 12903
>> committer: Francesco Chemolli <kinkie <at> squid-cache.org>
>> branch nick: trunk
>> timestamp: Sun 2013-06-09 22:35:58 +0200
>> message:
>>    Instruct clang not to treat unused command line arguments as errors
>> modified:
>>    acinclude/compiler-flags.m4
>
>
> Anyone known why we have the "-Wno-error=parentheses-equality" option in teh
> first place?
>  It would seem to me to be one of the warnings highlighting a coding
> guideline violation we need to fix in the sources. Not something to be
> suppressed.

I do, as I added it:

in case of
if (bool foo = somefunction()) {
}

gcc -Werror barfs unless it's expressed as:
if ((bool foo = somefunction())) {
}

(Continue reading)

Amos Jeffries | 10 Jun 2013 09:15
Picon
Favicon

SSl-bump wiki entry outdated

Alex, Christos - anybody else with good SSL-bump knowledge

Can somebody please udate http://wiki.squid-cache.org/Features/SslBump 
to document the options for bumping in 3.3 and recommend the safest 
possible bumping configuration.
It is currently still stuck on the 3.1 config examples and leading 
people to both warnings in 3.3 and unsafe configurations.

Cheers
Amos

Kinkie | 9 Jun 2013 22:40
Picon

Should we integrate libTrie into our build system?

Hi all,
  while attempting to increase portability to recent clang releases, I
noticed that libTrie hasn't benefited from the portability work that
was done in the past few years.

I can see three ways to move forward:
1- replicate these changes into libTrie
2- change libTrie to piggyback squid's configuration variables
3- fully integrate libTrie into squid's build system. Unless Robert
knows otherwise, squid is the only user of this library..

Comments?

--
    /kinkie

noc | 9 Jun 2013 07:53
Favicon

Build failed in Jenkins: 3.HEAD-amd64-CentOS-5.3 #2461

See <http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/2461/changes>

Changes:

[Alex Rousskov] Fix detection of concurrent ACLChecklist checks, avoiding !accessList asserts.

Concurrent checks are not supported, but it is possible for the same
ACLChecklist to be used for a sequence of checks, alternating fastCheck(void)
and fastCheck(list) calls. We needed a different/dedicated mechanism to detect
check concurrency (added ACLChecklist::occupied_), and we needed to preserve
(and then restore) pre-set accessList during fastCheck(list) checks.

------------------------------------------
[...truncated 58231 lines...]
make[4]: Leaving directory `<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_build/helpers/external_acl/file_userip'>
Making uninstall in kerberos_ldap_group
make[4]: Entering directory `<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_build/helpers/external_acl/kerberos_ldap_group'>
make[5]: Entering directory `<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_build/helpers/external_acl/kerberos_ldap_group'>
 ( cd
'/tmp/am-dc-26578/<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_inst/libexec'>
&& rm -f ext_kerberos_ldap_group_acl )
 ( cd
'/tmp/am-dc-26578/<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_inst/libexec'>
&& rm -f cert_tool )
make[5]: Leaving directory `<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_build/helpers/external_acl/kerberos_ldap_group'>
make[4]: Leaving directory `<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_build/helpers/external_acl/kerberos_ldap_group'>
Making uninstall in session
make[4]: Entering directory `<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_build/helpers/external_acl/session'>
 ( cd
'/tmp/am-dc-26578/<http://build.squid-cache.org/job/3.HEAD-amd64-CentOS-5.3/ws/btlayer-05-nodeps-esi/squid-3.HEAD-BZR/_inst/libexec'>
(Continue reading)

Alex Rousskov | 7 Jun 2013 19:02
Favicon

[PATCH] Fix detection of concurrent ACLChecklist checks, avoiding !accessList asserts

Hello,

    The attached patch prevents asserts when Squid reuses the same
Checklist object for multiple ACL checks. I missed one use case when
adding Checklist reuse controls for trunk r12859 (Boolean ACLs). The bug
can be triggered by a combination of log_access and access_log ACLs, for
example.

Concurrent checks are not supported, but it is possible for the same
ACLChecklist to be used for a sequence of checks, alternating
fastCheck(void) and fastCheck(list) calls. We needed a
different/dedicated mechanism to detect check concurrency (added
ACLChecklist::occupied_), and we needed to preserve (and then restore)
pre-set accessList during fastCheck(list) checks.

HTH,

Alex.
Tsantilas Christos | 7 Jun 2013 18:20
Picon

[PATCH] Sending root certificate for validation


This patch modify squid cert validation subsystem to sent to cert
validator helper the complete certificates chain, not only the
certificates sent by web server. This is may not be possible in all
cases, for example  in cases where the root certificate is not stored
locally.

This is a Measurement Factory project


Gmane