Mac Big Sur Mac mini M1

[Alexis81]

Good morning all,

I just bought a Mac Mini M1, to log in at work, I use Viscosity on my old MacBook Pro, it works great.

With the Mac Mini M1, with the same configuration when I click on the Detection button, I get the following message:

"No PKCS11 names could be detected. Please make sure the providor information is correct, the device is connected, and that it is not currently in use by a VPN connection."

Capture d’écran 2020-11-27 à 21.23.06.png (54.06 KiB) Viewed 10014 times

The PKI key is well connected and the PKCS11 is well informed. Do you have an idea ?

Capture d’écran 2020-11-27 à 21.21.53.png (58.13 KiB) Viewed 10014 times

Thank you.

[James]

Hi Alexis81,

The problem will be that the PKCS#11 driver you're using doesn't support Apple Silicon (ARM). Judging from the file path, the driver you appear to be using is the SafeNet Authentication Client (SAC). You'll need to get in touch with your IT administrator and see if they have an updated driver available that you can install.

Cheers,
James

[Alexis81]

Hello James,

I tried to install version Viscosity 1.8.4, on the Mac Mini M1, when I click on Name detection, it finds the certificate

Capture d’écran 2020-11-29 à 19.14.54.png (86.32 KiB) Viewed 9996 times

good then when I want to connect it says this to me:

2020-11-29 19:15:32: Viscosity Mac 1.8.6 (1546)
2020-11-29 19:15:32: Viscosity OpenVPN Engine Started
2020-11-29 19:15:32: Running on macOS 10.16.0
2020-11-29 19:15:32: ---------
2020-11-29 19:15:32: State changed to Connexion en cours
2020-11-29 19:15:32: Vérification du statut d'accessibilité de la connexion...
2020-11-29 19:15:32: La connexion est accessible. Tentative de démarrage de la connexion.
2020-11-29 19:15:32: Error: The TAP system extension could not be loaded.
2020-11-29 19:15:32: Could not start connection: Status failure.
2020-11-29 19:15:32: State changed to Déconnecté

Whereas with the version of Viscosity 1.9, I can't even detect the certificate ....

Can you help me because in this COVID time I am telecommuting and I need the VPN. Thank you

Alexis

[James]

Older versions of Viscosity are able to load the driver as they are Intel-only: they'll be running under Rosetta 2 emulation, and so able to load the Intel-only PKCS#11 driver. However older versions of Viscosity don't fully support macOS 11.

Viscosity 1.9+ natively supports Apple Silicon, and so it runs in native mode. As the PKCS#11 driver you are using is Intel-only, it's not able to be loaded. While macOS provides an "Open using Rosetta" option to force Intel emulation, I'm afraid this doesn't apply to Viscosity's background helper or OpenVPN.

You'll need to get in touch with your IT administrator and see if they have an updated driver available that you can install. This isn't a problem with Viscosity, but rather that the PKCS#11 driver being used does not support Apple Silicon/M1 Macs.

Cheers,
James