Search squid archive

Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed
From: Alex Ray <alexray@xxxxxxxxxxxxxxx>
Date: Mon, 27 Dec 2010 09:42:42 -0800
In-reply-to: <4D1558EB.2030602@xxxxxxxxxxxxx>
References: <AANLkTingwuoDonNsFr0ZnmTXnVrYuspGFWOzE5uxzkJ0@xxxxxxxxxxxxxx> <1293139884.14339.7.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <AANLkTikHQaf5UxHmk6xTPw9S=RXiTHQZdE6nn+zFycSi@xxxxxxxxxxxxxx> <1293149101.14339.91.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4D149756.6070204@xxxxxxxxxxxxx> <AANLkTikY5Z9emD4zvosM1pYJoBmLBYVy=0ikMcpFskAW@xxxxxxxxxxxxxx> <4D1558EB.2030602@xxxxxxxxxxxxx>

Looks like dynamic ssl certs are still broken as of 3.2.0.4:

microsoft.com uses an invalid security certificate.

The certificate is not trusted because it is self-signed.
The certificate is only valid for microsoft.com-----BEGIN CERTIFICATE-----

(Error code: sec_error_untrusted_issuer)

Follow-Ups:
- Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed
  - From: Amos Jeffries

References:
- Squid 3.2 - Dynamic SSL certs that aren't self-signed
  - From: Alex Ray
- Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed
  - From: Henrik Nordström
- Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed
  - From: Alex Ray
- Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed
  - From: Henrik Nordström
- Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed
  - From: Amos Jeffries

Prev by Date: Re: refusing connections
Next by Date: Re: size of squid binary
Previous by thread: Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed
Next by thread: Re: Squid 3.2 - Dynamic SSL certs that aren't self-signed
Index(es):
- Date
- Thread

[Index of Archives] [Linux Audio Users] [Samba] [Big List of Linux Books] [Linux USB] [Yosemite News]

Powered by Linux