Thank you for the reply. Thank you for confirming that the connections that are
started are not effected by the last ACL, thus clients not on acls prior would
be blocked and not allowed to access the cache. However ones that are would be
able to use the cache.
Jonathan Lee
Adult Student
Sent
The time constraints for termination do appear to lock out all new connections
until that timeframe has elapsed. My devices have connection errors during this
duration.
Just to confirm ssl_bump can not be used with time ? Because my connections
don’t work during the timeframe so that is a
On 24/04/24 17:27, Jonathan Lee wrote:
Hello fellow Squid users I wanted to ask a quick question for use with
termination would http access for cache still work with this type of setup and
custom refresh patterns?
I think it would terminate all but the clients and if they use the cache it
On 24/04/24 17:31, ivc chgaki wrote:
hello. i hve Samba DC and squid. i created user, then SPN, and then
exported keytab and imported him to squid. im using kerberos negotiate
helper but when i try go to internet i have popup window with
login/password and in cace.log log error
2024/04/21
Amos, thanks for the answer,
We will be waiting for full support of the TLS key logging.
Kind regards,
Ankor
сб, 27 апр. 2024 г. в 10:52, Amos Jeffries :
> On 25/04/24 19:57, Andrey K wrote:
> > Hello,
> >
> > Does squid 6.9 allow you to log TLS 1.3 keys so that you can then
> >
On 25/04/24 19:57, Andrey K wrote:
Hello,
Does squid 6.9 allow you to log TLS 1.3 keys so that you can then
decrypt traffic using Wireshark?
I found that there was an issue earlier with using tls_key_log to
decrypt TLS 1.3:
On 26/04/24 17:15, Jonathan Lee wrote:
aclblock_hourstime01:30-05:00ssl_bumpterminateallblock_hourshttp_accessdenyallblock_hours
In this a good way to time lock squid with times lock down?
That depends on your criteria/definition of "good".
Be aware that http_access only checks *new*
