Connect to an OpenVPN server whose certificate OpenSSL 3 rejects as too weak
The symptom log, the nmcli command and the .nmconnection path are taken directly from the Arch wiki NetworkManager section 'OpenVPN connections fail with OpenSSL ca md too weak error'. The second error form (VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak and 0A000086 certificate verify failed) is quoted from BBS 281136, solved with tls-cipher=DEFAULT:@SECLEVEL=0 alone. The CachyOS thread confirms the [vpn] section placement and that the user also changed cipher=AES-128-CBC to data-ciphers=AES-128-CBC. The wiki says the legacy provider is also needed, while both forum threads solved it without it, so the record's ordering (SECLEVEL first, legacy provider only if the error persists) is supported and the system-wide danger is stated. networkmanager-vpn-plugin-openvpn ships no D-Bus activation file, so nm-openvpn runs under NetworkManager and journalctl -u NetworkManager will show it. OpenSSL 3.6.4 is installed here. Not exercised: no OpenVPN plugin is installed on this machine.
@SECLEVEL=0 accepts weak keys and digests for this tunnel, which makes it easier to impersonate the VPN server. Enabling the OpenSSL legacy provider in /etc/ssl/openssl.cnf lowers this for every program on the machine. Treat both as temporary.
Symptom
A work or university OpenVPN profile that used to connect now fails every time. The NetworkManager journal shows:
nm-openvpn[14359]: OpenSSL: error:0A00018E:SSL routines::ca md too weak
nm-openvpn[14359]: Cannot load certificate file /home/user/.local/share/networkmanagement/certificates/my_issued_cert.crt
nm-openvpn[14359]: Exiting due to fatal error
or VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak followed by OpenSSL: error:0A000086:SSL routines::certificate verify failed.
Cause
The server's CA or client certificate is signed with a legacy digest (MD5 or SHA-1). OpenSSL 3's default security level rejects that, and Arch ships OpenSSL 3 and current OpenVPN. The certificate itself is the defect. The client is behaving correctly.
Fix
The real fix is on the server: ask the VPN administrator to reissue the CA and certificates with SHA-256 or better.
Until then, lower the security level for this one connection only:
nmcli connection show # find the VPN profile name
sudo nmcli connection modify 'vpn.example.com' +vpn.data tls-cipher=DEFAULT:@SECLEVEL=0
nmcli connection up 'vpn.example.com'
That writes tls-cipher=DEFAULT:@SECLEVEL=0 into the [vpn] section of /etc/NetworkManager/system-connections/vpn.example.com.nmconnection. If the old profile also used cipher=AES-128-CBC, one CachyOS user also needed data-ciphers=AES-128-CBC in the same section.
If the certificate also uses an algorithm that only OpenSSL's legacy provider implements, the Arch wiki describes enabling legacy = legacy_sect in /etc/ssl/openssl.cnf. Do that only if the error persists, because it applies system-wide.
Verify
nmcli connection up <name> succeeds. journalctl -u NetworkManager -b | grep nm-openvpn no longer shows ca md too weak. A tun0 interface exists.