Ho trovato una discussione sui forum di Apple con problemi simili ai tuoi. [ link ]
Ecco una soluzione che ha funzionato per un utente anche se mi concedo l'indulgenza di trovare la sua pratica di sicurezza piuttosto terrificante.
I granted client certificate's private key access to all applications and > set always trust certificate in the Keychain Access.
After that racoon successfully connected to vpn server. (there were about > 5 lines of errors in a log, but vpn worked)
Next, I returned certificate's trust policy to system defaults. (private > key access reverted automatically).
Now it works without errors.
Preferirei consigliare di provare questo metodo (prossimo post dall'origine)
I used Keychain Access to modify the private key's trust policy. However, instead of setting it to all application, I just gave access to /usr/sbin/racoon
.
Racoon è un processo che è (anche) utilizzato dalle soluzioni VPN di OS X.
Questo suggerimento si basa sulle seguenti righe:
1/20/16 3:08:02.860 PM com.apple.SecurityServer[84]: Authorization via securityd no longer supported
1/20/16 3:08:02.861 PM racoon[6269]: error -25308 errSecInteractionNotAllowed.
1/20/16 3:08:02.861 PM racoon[6269]: error -25308 errSecInteractionNotAllowed.
1/20/16 3:08:02.861 PM racoon[6269]: failed to sign.
1/20/16 3:08:02.861 PM racoon[6269]: failed to sign.
1/20/16 3:08:02.861 PM racoon[6269]: failed to get sign
1/20/16 3:08:02.861 PM racoon[6269]: failed to get sign
1/20/16 3:08:02.861 PM racoon[6269]: failed to allocate send buffer
1/20/16 3:08:02.861 PM racoon[6269]: failed to allocate send buffer
1/20/16 3:08:02.861 PM racoon[6269]: IKE Packet: transmit failed. (Initiator, Main-Mode Message 5).
1/20/16 3:08:02.861 PM racoon[6269]: failed to process packet.
1/20/16 3:08:02.861 PM racoon[6269]: failed to process packet.
1/20/16 3:08:02.861 PM racoon[6269]: Phase 1 negotiation failed.
1/20/16 3:08:02.861 PM racoon[6269]: Phase 1 negotiation failed.