Jim,
Looks like we ended up seeing the same problem in a kubernetes test case as
well:
https://github.com/kubernetes/kubernetes/issues/108956
-- Dims
On Thu, Mar 24, 2022 at 2:09 AM Jim Idle wrote:
> Having just upgraded to 1.18, I find that quite a few encrypted
> connections, for instance
Thanks for the additional info Jim. thanks! in our case it's a unit test
that we could control, but we just got worried about things in the wild
like your case for sure when we ship a go1.18 based kubectl.
thanks,
Dims
On Mon, Mar 28, 2022 at 8:41 PM Jim Idle wrote:
> Yes - look like it is for
Yes - look like it is for slightly different reasons. Apple have decided
on a new policy for verifying certificates and the certificate must have
either two (younger certs) or three (older certs) valid SCTs. I suspect
that you could re-issue your cert to comply with this, but I am not sure
about
Having just upgraded to 1.18, I find that quite a few encrypted
connections, for instance https to a Neptune instance on AWS, now fail with:
x509: “*.x.neptune.amazonaws.com” certificate is not standards
compliant
It seems to be related to this comment:
