Bug #17042
closedConfig OpenVPN Data Encryption is none cause Error on pfSense 2.9.0
0%
Description
I have an OpenVPN client configured with Data Encryption set to None. For some reason, we don't need data encryption due to our low network bandwidth.
After upgrading to pfSense Community Edition 2.9.0, the connection fails with:
OpenSSL: error:0308010C:digital envelope routines::unsupported: ... Algorithm (none : 0)
It looks like OpenSSL was also upgraded, and OpenVPN now relies on the newer OpenSSL 3.5, which does not allow the `none` cipher.
Therefore, we must enable Data Encryption. However, we expected pfSense to continue supporting Data Encryption = None, as it did in the previous version
JP Updated by Jim Pingle 20 days ago
- Status changed from New to Rejected
I can't reproduce this here. If I set Data Encryption Algorithms and Fallback Data Encryption Algorithm both to None (No Encryption) on the client and server, the tunnel still connects and passes traffic.
OpenVPN logs indicate it is using "None" as expected:
Aug 24 15:32:56 openvpn 99641 pfsense.home.arpa/udp4:198.51.100.23:37019 ******* WARNING *******: '--cipher none' was specified. This means NO encryption will be performed and tunnelled data WILL be transmitted in clear text over the network! PLEASE DO RECONSIDER THIS SETTING!
Also a lack of bandwidth is not a good excuse to skip encryption, but that's a different discussion.
MM Updated by Marcos M 20 days ago
- Related to Bug #17043: PHP error when removing all Data Encryption Algorithms from an OpenVPN instance added