You can set up your own internal CA. You then have the CA key (so can
generate certificates for any domain) and install the CA public
certificate on all client machines.
That CA can be anything from a local CA on the squid box, using a
central VM with something like XCA installed, all the way
Hey,
How should that work? That would require an ca to sign your selfsigney ca to be
able to issue valid public certs for all websites. If that would be possible,
then the whole concept of ssl security would be worth nothing. You cant create
valid certificates for such websites. You can only is
On Wednesday 05 September 2018 at 09:02:45, Arshad Ansari wrote:
> Hi All,
>
> I have setup squid 4.2 for forward proxy and caching. It is working fine
> when I am using self-signed certificate for SSL bump.
Good. Well done.
> However, our security requirement is to use only CA signed certific
Hi All,
I have setup squid 4.2 for forward proxy and caching. It is working fine when I
am using self-signed certificate for SSL bump.
However, our security requirement is to use only CA signed certificate and not
self-signed certificate.
I have tried various options like using Https and
