On 21/10/18 6:12 AM, Alex Rousskov wrote:
> On 10/20/18 7:47 AM, houheming wrote:
>> 1. Configure Squid to automatically generate origin server certificates
>> (signed by a configured CA X) and send them to browsers/clients that go
>> to those origin servers.
>
> OK.
>
>
>> If I configure squi
I am happy to announce the release of Squid-Cache 4.3 RPM's and
Debian+Ubuntu binaris.
I took a little project which some might like and other might not..
- TCP to SCP
- SCTP to TCP
Proxy servers.
The sources are at:
- https://github.com/elico/sctp-proxies
- http://gogs.ngtech.co.il/NgTech-LTD/s
I believe that eventually some of these features would be targeted by
the overall security community.
Security from one hand has encryption as a tool but it was already
proven that obscurity is not really security.
In fact until now from what I know many of the more sane clients in the
private a
On 10/20/18 12:00 AM, Troiano Alessio wrote:
> Also if client will use ESNI, the server should response with a certificate
> that will be in clear
Starting with TLS v1.3, the server certificate is encrypted.
Alex.
___
squid-users mailing list
squid-us
On 10/20/18 7:47 AM, houheming wrote:
> 1. Configure Squid to automatically generate origin server certificates
> (signed by a configured CA X) and send them to browsers/clients that go
> to those origin servers.
OK.
> If I configure squid like:
>
> https_port 180.97.33.107:443 ...
> https_po
On Saturday 20 October 2018 at 16:53:12, Mujtaba Hassan Madani wrote:
> Hi,
>
> now it works through URL
>
> http://196.202.134.253:3128/squid-internal-mgr/info instead of
> http://proxy.com:3128/squid-internal-mgr/info
Yes, that is because proxy,com does not belong to you - it points to someon
Hi,
now it works through URL
http://196.202.134.253:3128/squid-internal-mgr/info instead of
http://proxy.com:3128/squid-internal-mgr/info
From: squid-users on behalf of
Antony Stone
Sent: Saturday, October 20, 2018 2:08:32 PM
To: squid-users@lists.squid-ca
On Saturday 20 October 2018 at 15:59:36, Mujtaba Hassan Madani wrote:
> Hi Antony,
>
> this is the first IP Connection to 34.194.132.99 failed.
That is the address which "proxy,com" resolves to on my machine too.
> the IP of my server is 196.202.134.253
So, does this give you any clues as to
Hi Antony,
this is the first IP Connection to 34.194.132.99 failed.
the IP of my server is 196.202.134.253
i got the instruction of changing of from below default setting form URL
http_access allow localhost manager
http_access deny manager so i can login through
browser to the cache manage
Hi Alex & Amos,
Thanks for your replies, sorry for my poor English, I will add more information.
#1
1. Configure Squid to automatically generate origin server certificates
(signed by a configured CA X) and send them to browsers/clients that go
to those origin servers.
This is my situati
On Saturday 20 October 2018 at 14:56:33, Mujtaba Hassan Madani wrote:
> Hi Amos,
>
>I get attached message when trying to access cache manger through web
> interface below is my full URL
>
> http://proxy.com:3128/squid-internal-mgr/info
1. What IP address does "proxy.com" resolve to on your
Hi Amos,
I get attached message when trying to access cache manger through web
interface below is my full URL
http://proxy.com:3128/squid-internal-mgr/info
according to squid.org feedback
https://wiki.squid-cache.org/action/show/Features/CacheManager?action=show&redirect=SquidFaq%2FCacheM
12 matches
Mail list logo
