4 ms·
Safari is terrible with client certs - it seems to store the default on a per page basis rather than per domain. Changing that involves diving deep into keychai
by iso947 7y ago
Safari is terrible with client certs - it seems to store the default on a per page basis rather than per domain. Changing that involves diving deep into keychain.
Chrome usually works but yesterday a colleague had problems where the dialog asking which cert to use wouldn’t respond.
Firefox just works.
It’s a shame that certificates aren’t used more widely. They don’t work at all in captive portal pages on OS X or iphones :(