On 1/11/2016 6:31 a.m., Eduardo Carneiro wrote:
> Hi all.
>
> I have a strange authentication issue in my squid 3.5.19. My workstations
> only can authenticate if they are entered into the domain. When they doesn't
> entered into the domain, I access any URL on browser (Firefox and Chrome
> tested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Google and so is not too conducive to caching the end user. One problem
anymore - one less, what's the difference? When we begin to beat - start
to cry. In general, the year in IT - eternity. During this time,
everything can happen. So relax, cousi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When the future comes - then we will worry. What wonder, then?
October 2017 is not tomorrow.
01.11.2016 4:13, L. A. Walsh пишет:
> Google is pushing this for all websites by October 2017
>
> One issue to be "caught" are subordinated CA certs tha
Google is pushing this for all websites by October 2017
One issue to be "caught" are subordinated CA certs that can
allow one vector for generating certs accepted by browsers w/o
importing any new certs.
Some of the info on the cert page:
https://www.certificate-transparency.org/what-is-ct
Hi all.
I have a strange authentication issue in my squid 3.5.19. My workstations
only can authenticate if they are entered into the domain. When they doesn't
entered into the domain, I access any URL on browser (Firefox and Chrome
tested) and I'm not able authenticate on the boxes that are shown
