Re: [squid-users] Re: Hotmail issue in squid 3.4.4
On 10/06/2014 5:09 p.m., vin_krish wrote: Hi Eliezer, Sorry for late reply as I was busy with some other issues. But I tested long back but was not able to reply you. I tested with your bash script but it throws error all time as: 2014/06/10 10:33:13| Accepting HTTP Socket connections at local=[::]:3128 remote=[::] FD 19 flags=9 2014/06/10 10:33:13| Accepting NAT intercepted SSL bumped HTTPS Socket connections at local=[::]:3129 remote=[::] FD 20 flags=41 2014/06/10 10:33:13| WARNING: ssl_crtd #Hlpr0 exited This is the problem. Why did that happen? Usually we find this is from incorrect access permissons to the /etc/squid3/ssl_cert/ssl_db or corrupted file(s) there. 2014/06/10 10:33:13| Too few ssl_crtd processes are running (need 1/10) 2014/06/10 10:33:13| Closing HTTP port [::]:3128 2014/06/10 10:33:13| Closing HTTPS port [::]:3129 2014/06/10 10:33:13| storeDirWriteCleanLogs: Starting... 2014/06/10 10:33:13| Finished. Wrote 0 entries. 2014/06/10 10:33:13| Took 0.00 seconds ( 0.00 entries/sec). FATAL: The ssl_crtd helpers are crashing too rapidly, need help! and my configuration is: http_port 3128 https_port 3129 intercept ssl-bump generate-host-certificates=on dynamic_cert_mem_cache_size=16MB cert=/etc/squid3/ssl_cert/myCA.pem sslcrtd_program /usr/local/squid/libexec/ssl_crtd -s /etc/squid3/ssl_cert/ssl_db -M 16MB sslcrtd_children 10 I have gone through forum and search also, as they specify about the change of permission and ownership to my user 'squid' to the ssl directory, but it didn't work. Did you run the ssl_crtd tool as that user when you created it? Amos
Re: [squid-users] squid with qlproxy on fedora 20 not working for https traffic
On 10/06/2014 1:08 p.m., MrErr wrote: Hi have spent two days googling and going through these forums and have not been able to get https filtering working. I am new to all of this kind of networking stuff. So i do need a lot of help :) I have a gateway machine which is my rotuer. On this same gateway i have squid and qlproxy installed. I want to be able to filter on both http and https. Only http filtering works now, but not https. So i am not able to make google default to safe search. I am going to paste my configuration files, so my apologies for the long files. My squid.conf is acl localnet src 192.168.13.0/24 acl localnet src 127.0.0.1/8 acl wanip src 97.90.225.128 acl SSL_ports port 443 acl Safe_ports port 80# http acl Safe_ports port 8080 # http acl Safe_ports port 21# ftp acl Safe_ports port 443 # https acl Safe_ports port 70# gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535# unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT http_access deny !Safe_ports http_access allow CONNECT SSL_ports http_access deny CONNECT !SSL_ports http_access allow localhost manager http_access deny manager http_access deny to_localhost http_access allow localnet http_access allow wanip http_access allow localhost http_access deny all http_port 192.168.13.1:3128 http_port 192.168.13.1:3129 intercept https_port 192.168.13.1:3130 intercept ssl-bump cert=/etc/squid/myCA.pem You are using server-first bumping. I dont think that works without the certificate generator being configured. It just means Squid takes the server cert and uses it as the basis for the one delivered to the client. acl qlproxy_https_exclusions dstdomain /etc/opt/quintolabs/qlproxy/squid/https_exclusions.conf acl qlproxy_https_targets dstdomain /etc/opt/quintolabs/qlproxy/squid/https_targets.conf ssl_bump none localhost ssl_bump server-first qlproxy_https_targets always_direct allow all cache_dir ufs /var/spool/squid 100 16 256 coredump_dir /var/spool/squid refresh_pattern ^ftp: 144020% 10080 refresh_pattern ^gopher: 14400% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 icap_enable on icap_preview_enable on icap_preview_size 4096 icap_persistent_connections on icap_send_client_ip on icap_send_client_username on icap_client_username_header X-Client-Username icap_service qlproxy1 reqmod_precache 0 icap://127.0.0.1:1344/reqmod icap_service qlproxy2 respmod_precache 0 icap://127.0.0.1:1344/respmod adaptation_access qlproxy1 allow all adaptation_access qlproxy2 allow all my iptables are Hint: you may want to look at the tool ferm to make these rules simpler, faster and easier to read. It generates rules a bit more optimal than this while also allowing easier config than iptables directy. (and does IPv6 firewall config transparently!). # Generated by iptables-save v1.4.19.1 on Mon Jun 9 20:03:48 2014 *nat :PREROUTING ACCEPT [683:114416] :INPUT ACCEPT [477:31902] :OUTPUT ACCEPT [441:27340] :POSTROUTING ACCEPT [2:176] :OUTPUT_direct - [0:0] :POSTROUTING_ZONES - [0:0] :POSTROUTING_ZONES_SOURCE - [0:0] :POSTROUTING_direct - [0:0] :POST_external - [0:0] :POST_external_allow - [0:0] :POST_external_deny - [0:0] :POST_external_log - [0:0] :POST_internal - [0:0] :POST_internal_allow - [0:0] :POST_internal_deny - [0:0] :POST_internal_log - [0:0] :POST_public - [0:0] :POST_public_allow - [0:0] :POST_public_deny - [0:0] :POST_public_log - [0:0] :PREROUTING_ZONES - [0:0] :PREROUTING_ZONES_SOURCE - [0:0] :PREROUTING_direct - [0:0] :PRE_external - [0:0] :PRE_external_allow - [0:0] :PRE_external_deny - [0:0] :PRE_external_log - [0:0] :PRE_internal - [0:0] :PRE_internal_allow - [0:0] :PRE_internal_deny - [0:0] :PRE_internal_log - [0:0] :PRE_public - [0:0] :PRE_public_allow - [0:0] :PRE_public_deny - [0:0] :PRE_public_log - [0:0] -A PREROUTING -j PREROUTING_direct -A PREROUTING -j PREROUTING_ZONES_SOURCE -A PREROUTING -j PREROUTING_ZONES -A OUTPUT -j OUTPUT_direct -A POSTROUTING -j POSTROUTING_direct -A POSTROUTING -j POSTROUTING_ZONES_SOURCE -A POSTROUTING -j POSTROUTING_ZONES -A POSTROUTING_ZONES -o p6p1 -g POST_internal -A POSTROUTING_ZONES -o p2p1 -g POST_external -A POSTROUTING_ZONES -g POST_public -A POST_external -j POST_external_log -A POST_external -j POST_external_deny -A POST_external -j POST_external_allow -A POST_external_allow ! -i lo -j MASQUERADE -A POST_internal -j POST_internal_log -A POST_internal -j POST_internal_deny -A POST_internal -j POST_internal_allow -A POST_public -j POST_public_log -A POST_public -j POST_public_deny -A
[squid-users] Re: Hotmail issue in squid 3.4.4
Hi Amos, When I created 'ssl_crtd', by default it had 'root' permission, then I changed to my user 'squid' and run. After changing to my user also error comes. But when I ran at command prompt with /usr/local/squid/libexec/ssl_crtd -c -s /etc/squid3/ssl_cert/ssl_db it initialized, then I tried to run from squid conf as mentioned in the doc, sslcrtd_program /usr/local/squid/libexec/ssl_crtd -s /etc/squid3/ssl_cert/ssl_db -M 16MB then the error comes: FATAL: The ssl_crtd helpers are crashing too rapidly, need help! Thanks for reply. Regards, krish -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Hotmail-issue-in-squid-3-4-4-tp4666020p4666282.html Sent from the Squid - Users mailing list archive at Nabble.com.
WG: [squid-users] Squid 3.3.8 NTLM problems
Hello Amos,
thanks for your suggestions on the config, I changed the lines as you proposed.
But I'm still having the issue with the multiple popups at first logon with IE.
Do you have any idea to this?
Thanks and regards
Mana
-Ursprüngliche Nachricht-
Von: Amos Jeffries [mailto:squ...@treenet.co.nz]
Gesendet: Donnerstag, 5. Juni 2014 11:32
An: squid-users@squid-cache.org
Betreff: Re: [squid-users] Squid 3.3.8 NTLM problems
On 5/06/2014 7:54 p.m., Manfred Mayer IT wrote:
Hi there,
I'm trying to setup a Squid 3.3.8 on a Ubuntu 14.04 and I'm having some
problems with the NTLM authentication. We have three ports, 2 are with
authentication (3128 and 3129). The server is joined to a Windows 2008 domain
and authentication works fine on machines that are also in this domain. But
on non-domain machines, in Internet Explorer I get the authentication popup
up to 6 times, then I get Access denied and only after a reload, the site
is viewed correctly. With our old Squid 2.7 I just had to login once. I tried
to adapt our existing 2.7-config for squid3, maybe I made a mistake, can
someone help me to fix this error? Or is this a smb/winbind related error?
Please rune squid -k check and fix the errors it mentions. There are quite a
few lines of the config below which are unnecessary or wrong in squid-3.3.
I've mentioned below a few of the extra changes that are not easily detected
like that..
http_port 3128
http_port 3129
http_port 4711
logformat squid %{%d.%m.%Y %H:%M:%S}tl.%03tu %6tr %a %[un %Ss/%03Hs
%st %rm %ru %Sh/%a %mt
You should not re-define the native Squid log format.
Please use a different name. Although its worth noting that this logformat is
never being used anyway due to emulate_httpd_log on.
hierarchy_stoplist cgi-bin ?
acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY
the above three lines can go.
cache_dir ufs /var/cache/squid 100 16 256 cache_access_log
stdio:/var/log/squid3/access.log cache_log /var/logs/cache.log
cache_log /var/log/squid3/cache.log
You can only have one debug log for Squid. Temove the top cache_log line.
cache_store_log none
emulate_httpd_log on
log_fqdn on
auth_param ntlm program /usr/bin/ntlm_auth
--helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 30
auth_param basic program /usr/bin/ntlm_auth
--helper-protocol=squid-2.5-basic auth_param basic children 5
auth_param basic realm Squid proxy-caching web server auth_param basic
credentialsttl 2 hours
refresh_pattern ^ftp: 144020% 10080
refresh_pattern ^gopher:14400% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern (Release|Packages(.gz)*)$ 0 20% 2880
refresh_pattern . 0 20% 4320
acl localhost src 127.0.0.1/32
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 563 4434 7004
acl Safe_ports port 80 # http
acl Safe_ports port 180 # http
acl Safe_ports port 181 # http
acl Safe_ports port 182 # http
acl Safe_ports port 183 # http
acl Safe_ports port 184 # http
acl Safe_ports port 185 # http
acl Safe_ports port 186 # http
acl Safe_ports port 187 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 563 # https, snews
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT
acl firstport myport 3128 # (first local socket TCP port)
acl secport myport 3129 # (second local socket TCP port)
acl thirdport myport 4711 # (third local socket TCP port)
acl SSL method CONNECT
always_direct allow SSL
Why not simplify with always_direct allow CONNECT ?
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
acl local-servers dstdomain int.rapunzel.de always_direct allow
local-servers acl our_networks_new src 172.16.0.0/16 acl goodlocalips
src /etc/squid3/goodlocalips
http_access allow localhost
http_access allow goodlocalips
acl AuthorizedUsers proxy_auth REQUIRED http_access allow firstport
our_networks_new AuthorizedUsers http_access allow secport
our_networks_new AuthorizedUsers http_access allow thirdport
http_access deny all always_direct allow all icp_access allow all
forwarded_for on never_direct allow all
So you have a series of always_direct allow terminated by an allow all.
Then a single never_direct allow all. But you have no cache_peer lines at all.
So all these always/never routing rules are just a waste of CPU cycles and
time. You can drop the always_direct and never_direct lines completely.
Amos
Email secured by [Rapunzel IT]
Rapunzel Naturkost
Re: [squid-users] Squid SSL Bump transparently CONNECT for another proxy
Hello, 1) But because of firewall rules settings, the only way we can connect to internet is through PROXY2. PROXY1 will not be allowed to connect to internet. So cannot go to internet via PROXY1 and still needs to bump the connection to see the decrypted traffic. So what are my options? Should I be looking towards changing squid code to handle this scenario? Thanks, Jatin On Sun, Jun 8, 2014 at 12:20 PM, Amos Jeffries squ...@treenet.co.nz wrote: On 8/06/2014 10:03 a.m., Jatin Bhasin wrote: Hello, 1) I have to bump the SSL request because I want to pass the decrypted traffic to the eCap adapter so that I can look for viruses in the traffic and block them if found. 2) I cannot inroduce Proxy1 in the client browser. The only option I have is PROXY1 sitting in the middle of Client and PROXY2 and then PROXY1 should decrypt the traffic and send it to the ecap adapter for virus checking and block them. Okay so far so good. Use intercept rules in the PROXY1 machines networking stack *without* the intercept flag in squid.conf. PROXY1 does not have to do any network level un-NAT hacks to process requests destined explicitly to itself or any other HTTP proxy. You may encounter problems getting the decoded traffic back to PROXY2 though. The released Squid versions do not yet generate CONNECT requests for upsream unless one is intercepting port 443 traffic and *bypassing* the ssl-bump. PROXY1 will try to use port 443 HTTPS itself. Amos
[squid-users] squid 3.3.10 under freeBSD
Hi ! I maintain a package fort he pfSense project and need some help: We’re running squid 3.3.10 under freebsd 8.3 release p16 and i’m gettin gtting errors when trying to start squid: 2014/06/10 11:02:43 kid1| WARNING: failed to find or read error text file error-details.txt 2014/06/10 11:02:43 kid1| sendto FD 36: (1) Operation not permitted 2014/06/10 11:02:43 kid1| ipcCreate: CHILD: hello write test failed 2014/06/10 11:03:06 kid1| Starting Squid Cache version 3.3.10 for i386-portbld-freebsd8.3... 2014/06/10 11:03:06 kid1| parse error while reading template file: /usr/pbi/squid-i386/etc/squid/errors/de/error-details.txt 2014/06/10 11:03:06 kid1| Unable to load default error language files. Reset to backups. 2014/06/10 11:03:06 kid1| parse error while reading template file: /usr/pbi/squid-i386/etc/squid/errors/templates/error-details.txt 2014/06/10 11:03:06 kid1| WARNING: failed to find or read error text file error-details.txt 2014/06/10 11:03:06 kid1| sendto FD 31: (1) Operation not permitted 2014/06/10 11:03:06 kid1| ipcCreate: CHILD: hello write test failed 2014/06/10 11:04:03 kid1| Starting Squid Cache version 3.3.10 for i386-portbld-freebsd8.3... 2014/06/10 11:04:03 kid1| parse error while reading template file: /usr/pbi/squid-i386/etc/squid/errors/de/error-details.txt 2014/06/10 11:04:03 kid1| Unable to load default error language files. Reset to backups. 2014/06/10 11:04:03 kid1| parse error while reading template file: /usr/pbi/squid-i386/etc/squid/errors/templates/error-details.txt 2014/06/10 11:04:03 kid1| WARNING: failed to find or read error text file error-details.txt 2014/06/10 11:04:03 kid1| sendto FD 40: (1) Operation not permitted 2014/06/10 11:04:03 kid1| ipcCreate: CHILD: hello write test failed I already saw a post on the squid-users list on nabble here: http://squid-web-proxy-cache.1019090.n4.nabble.com/WARNING-no-suid-setuid-0- 1-Operation-not-permitted-td4658291.html but it was of no help… squid does not run at all, does not server any requests and states that there is no copy running… does anyone know, what to do ? regards, Martin
Re: [squid-users] memory_cache_shared no support for atomic operations
Ah OK, thank you very much. If someone could fix the documentation and add a note that is only 64 bit supported.. Thanks 2014-06-10 1:47 GMT-03:00 Amos Jeffries squ...@treenet.co.nz: On 10/06/2014 10:10 a.m., Eliezer Croitoru wrote: On 06/10/2014 12:43 AM, Cassiano Martin wrote: Yes its 32 bit custom built OS As far as I can remember the shared memory needed 64bit OS and HW. I am not 100% sure yet. Yes 64-bit atomics are required. And for now it is also restricted to GNU-style atomic operations. Although with a bit of patching these can be replaced with C++11 standardized atomics. Amos
[squid-users] cache problem
Hallo I have a problem with cache files. We need to download a gpg file (size 82 MB) and we are behind a firewall with virusscanner. The download stall 4-5 times. After the first stall the cached file will be deleted on the cache. But we need this file more then one time from different locations to be download (from cache). My Settings: maximum_object_size 200 MB cache_dir ufs /var/spool/squid 50 56 256 refresh_pattern -i .(deb|gpg)$ 129600 100% 129600 override-expire ignore-no-cache max-stale=99 Squid Version: 2.7.STABLE9-4.1 Karl Heinz.
Re: [squid-users] memory_cache_shared no support for atomic operations
On 06/09/2014 07:10 PM, Eliezer Croitoru wrote: On 06/10/2014 12:43 AM, Cassiano Martin wrote: Yes its 32 bit custom built OS As far as I can remember the shared memory needed 64bit OS and HW. I am not 100% sure yet. Eliezer I am not sure but vaguely recall that it works on 32bit when the number of workers is 1. Marcus
Re: [squid-users] Squid 3.4.5 Centos RPMs is OUT.
Hi, I'm using your squid 3.3.11 RPM for CentOS 6.5 64-bit; will there be the bugfix release 3.3.12 RPM for CentOS 6.5 also available? Thanks, Walter
[squid-users] SSLBump and client certificate forward
Hi, I'm trying to put sslbump to work but I can't capture and forward the client certificate when asked by the remote server. I've followed the instruciont on Features/BumpSslServerFirst Features/DynamicSslCert and I've also configured stunnel as Amos Jeffries has suggested here in the past. Do you have any other tip? If it helps, this is the related lines of my squid.conf: # As I'm using port 3128 to listen the stunnel forwarded traffic http_port 3129 ssl-bump cert=/etc/ssl/squid/squid.pem dynamic_cert_mem_cache_size=4MB generate-host-certificates=on always_direct allow all ssl_bump server-first all # the following two options are unsafe and not always necessary: sslproxy_cert_error allow all sslproxy_flags DONT_VERIFY_PEER sslcrtd_program /usr/libexec/squid/ssl_crtd -s /var/lib/squid/ssl_db -M 4MB sslcrtd_children 5 I'm currently running squid-3.4.5 on a gentoo server. But I've also tried with version 3.3.12. I need to pass client certificate (IE8) to at least two websites. One returns to me a 403 error and the other a 502. Mr. Rousskov, answering your question: yes, client certificate authentication does work through squid when no ssl_bump is active. Thanks for your attention. P.S.: Mr. Rousskov, thanks for your kind reply and sorry for the inconvenience :) -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/SSLBump-and-client-certificate-forward-tp4666290.html Sent from the Squid - Users mailing list archive at Nabble.com.
RE: [squid-users] squid 3.3.10 under freeBSD
perhaps i should also tell you that FreeBSD is a 64-bit Version... From: mar...@fuchs-kiel.de To: squid-users@squid-cache.org Date: Tue, 10 Jun 2014 10:56:38 + Subject: [squid-users] squid 3.3.10 under freeBSD Hi ! I maintain a package fort he pfSense project and need some help: We’re running squid 3.3.10 under freebsd 8.3 release p16 and i’m gettin errors when trying to start squid: 2014/06/10 11:02:43 kid1| WARNING: failed to find or read error text file error-details.txt 2014/06/10 11:02:43 kid1| sendto FD 36: (1) Operation not permitted 2014/06/10 11:02:43 kid1| ipcCreate: CHILD: hello write test failed 2014/06/10 11:03:06 kid1| Starting Squid Cache version 3.3.10 for i386-portbld-freebsd8.3... 2014/06/10 11:03:06 kid1| parse error while reading template file: /usr/pbi/squid-i386/etc/squid/errors/de/error-details.txt 2014/06/10 11:03:06 kid1| Unable to load default error language files. Reset to backups. 2014/06/10 11:03:06 kid1| parse error while reading template file: /usr/pbi/squid-i386/etc/squid/errors/templates/error-details.txt 2014/06/10 11:03:06 kid1| WARNING: failed to find or read error text file error-details.txt 2014/06/10 11:03:06 kid1| sendto FD 31: (1) Operation not permitted 2014/06/10 11:03:06 kid1| ipcCreate: CHILD: hello write test failed 2014/06/10 11:04:03 kid1| Starting Squid Cache version 3.3.10 for i386-portbld-freebsd8.3... 2014/06/10 11:04:03 kid1| parse error while reading template file: /usr/pbi/squid-i386/etc/squid/errors/de/error-details.txt 2014/06/10 11:04:03 kid1| Unable to load default error language files. Reset to backups. 2014/06/10 11:04:03 kid1| parse error while reading template file: /usr/pbi/squid-i386/etc/squid/errors/templates/error-details.txt 2014/06/10 11:04:03 kid1| WARNING: failed to find or read error text file error-details.txt 2014/06/10 11:04:03 kid1| sendto FD 40: (1) Operation not permitted 2014/06/10 11:04:03 kid1| ipcCreate: CHILD: hello write test failed I already saw a post on the squid-users list on nabble here: http://squid-web-proxy-cache.1019090.n4.nabble.com/WARNING-no-suid-setuid-0- 1-Operation-not-permitted-td4658291.html but it was of no help… squid does not run at all, does not server any requests and states that there is no copy running… does anyone know, what to do ? regards, Martin
Re: [squid-users] Squid 3.4.5 Centos RPMs is OUT.
I am about to release a second revision of 3.4.5 since there was probably an issue with the build node which might cause extra dependencies and issues with the first revision. If it is indeed needed I will try my best to release a new version of 3.3.12 later. Just try to remind me about it if it pop out of my memory in two weeks. Eliezer On 06/10/2014 05:17 PM, Walter H. wrote: Hi, I'm using your squid 3.3.11 RPM for CentOS 6.5 64-bit; will there be the bugfix release 3.3.12 RPM for CentOS 6.5 also available? Thanks, Walter
Re: [squid-users] Squid 3.4.5 Centos RPMs is OUT.
Squid 3.4.5-2 and 3.3.12-1 is out. Eliezer On 06/10/2014 05:17 PM, Walter H. wrote: Hi, I'm using your squid 3.3.11 RPM for CentOS 6.5 64-bit; will there be the bugfix release 3.3.12 RPM for CentOS 6.5 also available? Thanks, Walter
Re: [squid-users] Re: Squid 3.4.x Videos/Music Booster
I've rewritten your scripts to C++ native binary. If you'd like to include it on your package, feel free to contact me. Thanks 2014-06-09 16:42 GMT-03:00 Stakres vdoc...@neuf.fr: Hi All, Version https://sourceforge.net/projects/squidvideosbooster/ *1.02* is released including: - Scripts in Perl, Ruby and Python. - Special key 'porn' to de-duplicate or not Porn web sites Bye Fred -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-4-x-Videos-Music-Booster-tp4666154p4666272.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Re: Squid 3.4.x Videos/Music Booster
Anyway, here it is. Compile it with g++ booster.cpp -lcurl http://pastebin.com/raw.php?i=5HKk8rQq Admins, sorry about this off-topic! 2014-06-11 1:10 GMT-03:00 Cassiano Martin cassi...@polaco.pro.br: I've rewritten your scripts to C++ native binary. If you'd like to include it on your package, feel free to contact me. Thanks 2014-06-09 16:42 GMT-03:00 Stakres vdoc...@neuf.fr: Hi All, Version https://sourceforge.net/projects/squidvideosbooster/ *1.02* is released including: - Scripts in Perl, Ruby and Python. - Special key 'porn' to de-duplicate or not Porn web sites Bye Fred -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-4-x-Videos-Music-Booster-tp4666154p4666272.html Sent from the Squid - Users mailing list archive at Nabble.com.
