![]() > trust chain back to the root CA that it *does* have. > that intermediate on the wire, in order for the server to complete the > intermediate CA which isn't known to the server. > The problem here is normally that your own cert is signed by an > do not believe the problem is with the certs themselves. > machine in the office using the Windows Cisco An圜onnect client, so I > successfully connected to the VPN with my CAC on a Windows test > On Mon, at 14:51 -0500, Adam Allgood wrote: On Mon, at 3:41 PM David Woodhouse wrote: ![]() ![]() I no longer got aĬertificate validation failure, and after telling the shill program inĬhromeOS to stop destroying my tun0 devices (sudo stop shill followedīy sudo start shill BLACKLISTED_DEVICES="tun0,br0"), I got a stable Needed (unless it's causing the problems below) - and I exported itįrom the chrome certificate manager as a. Thanks so much for the response! I think I found the issuer cert
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |