Hi,
I'm trying to use the email notification feature specified in the document.
http://www.squid-cache.org/Doc/config/mail_program/
http://www.squid-cache.org/Doc/config/cache_mgr/
http://www.squid-cache.org/Doc/config/mail_from/
Basically, if the Squid proxy server dies, I can receive an email
n
Amos,
You rock it,
Thanks a lot, now its working pretty well.
I was partialy aware of PHP limitation when used to build external
helpers any way I gave it not too much importance since was working
fine, I will rewrite code in python ASAP, I appreciate your
recommendations.
Please if is not too mu
On 31/01/2015 2:00 p.m., Darren B. wrote:
> Hi
>
> I am trying to set up a router that is inline between the clients and
> the internet.
>
> Everything is working as far as proxy operations, however i am now
> trying to set up a splash page that new clients are shown when they
> first connect.
>
Hi
I am trying to set up a router that is inline between the clients and
the internet.
Everything is working as far as proxy operations, however i am now
trying to set up a splash page that new clients are shown when they
first connect.
The splash page is served off a copy of nginx running
Hi
I am trying to set up a router that is inline between the clients and
the internet.
Everything is working as far as proxy operations, however i am now
trying to set up a splash page that new clients are shown when they
first connect.
The splash page is served off a copy of nginx running
On 29/01/2015 11:59 a.m., HackXBack wrote:
> Dear Amos,
>
> root@dotspot:~# /usr/lib/squid/ssl_crtd -d
> /usr/lib/squid/ssl_crtd: Uninitialized SSL certificate database directory: .
> To initialize, run "ssl_crtd -c -s ".
>
> no debug msg !!?
>
That was the debug message:
"
Uninitialized SSL
On 31/01/2015 9:15 a.m., Alberto Perez wrote:
> Hello to everyone,
>
> First of all thanks for the support and for this awesome product.
>
Welcome. Thank You for getting the use of authorization vs
authentication correct in your question :-) so nice not to have to start
with clarifying that.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I mean it not written yet. ;)
But looks like time to. ;)
Regarding FAQ - I think, need to clearly differentiate interception
bumping and reverse proxy. And focus to some near-SSL Squid details.
Somebody's don't understand, how PKI works in general.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/01/2015 12:19 a.m., Yuri Voinov wrote:
>
> Amos,
>
> this question is already ready for FAQ.
>
> Time to write article in Squid Wiki? :)
Where did you find that? must be hidden so deeply I missed it
yesterday when lookign for a ref.
Regardin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Omg.
You ssl_crtd uses openssl, which uses public CA certs bundle.
I'm about it.
31.01.2015 2:56, HackXBack пишет:
> Yuri Voinov ,
> what you are talking about ?
> I used self signed CA, the problem is that every hour i got error in
> cache.log
Yuri Voinov ,
what you are talking about ?
I used self signed CA, the problem is that every hour i got error in
cache.log and squid keep restarting
"Re: FATAL: The ssl_crtd helpers are crashing too rapidly, need help! "
and after i remove db
rm -rf /etc/squid/ssl_db/certs
and then create again
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The point following.
OpenSSL itself contains CAs derived from Mozilla bundle.
This CA bundle is NOT complete and NOT contains most intermediate
certificates.
I was forced to find and install over 40 CA's.
In particular, Symantec intermediate and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Man,
which SSL CA bundle are you using?
31.01.2015 2:16, HackXBack пишет:
> Dear Amos ,
> please answer me because crashing increased , now it happen every hour, so
> every hour i need to delete old ssl db and create new one then restart
squid
> t
Dear Amos ,
please answer me because crashing increased , now it happen every hour, so
every hour i need to delete old ssl db and create new one then restart squid
to make it works !!
how i can tune this issue to solve it i need you in this bug,
Thanks Mate.
--
View this message in context:
htt
Hello to everyone,
First of all thanks for the support and for this awesome product.
I'm developing a captive portal with squid 3.4.9 over ubuntu 14.04
Here is my external acl configuration
external_acl_type session_active_def ipv4 %SRC
/etc/squid3/captive/sessionHelper.php concurrency=100 ch
Dear all,
Many Thanks for help, an fast answers case closed.
Sorry for bothering you.
best regrads
Chris
Am 30.01.2015 um 01:43 schrieb Christian Kundela:
Dear all,
I have problems setting up explicit proxy. (interrcept tcp 80 no problem)
If i doaself signed Cert, and i install it in Firefo
When I look to see what's available after adding backports to sources.list I do
see the 3.4 package:
root@##:/etc/squid3# apt-cache madison squid3
squid3 | 3.4.8-5~bpo70+1 | http://ftp.debian.org/debian/
wheezy-backports/main i386 Packages
squid3 | 3.1.20-2.2+deb7u2 | http://ftp.us.d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amos,
this question is already ready for FAQ.
Time to write article in Squid Wiki? :)
This question popups every week.
WBR, Yuri
30.01.2015 10:42, Amos Jeffries пишет:
> On 30/01/2015 1:43 p.m., Christian Kundela wrote:
>> Dear all,
>>
>> I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian,
for SSL Bump Squid expects only self-signed root CA. Not server signed -
it only appropriate on a reverse proxy.
WBR, Yuri
30.01.2015 6:43, Christian Kundela пишет:
> Dear all,
>
> I have problems setting up explicit proxy. (interrcept
> It is not true.
> Squid3 in debian is newer then 3.1 as far as I remember and if it's
> not
> in the main repos then use the backports for it.
No, 3.1.20 is the latest in stable release (wheezy)
> > It is but it’s the latest version available through apt-get on
> > Debian 7 without adding backp
Hey Bobby,
It is not true.
Squid3 in debian is newer then 3.1 as far as I remember and if it's not
in the main repos then use the backports for it.
It is recommended that you will use a newer version of squid.
If for your environment 3.1 works fine then I guess you can say that it
works and th
21 matches
Mail list logo
