May. 20, 2008
Last weeks OpenSSL issues in Debian based distributions didn't go unnoticed for most of us. The introduction of openssl-vulnkey screwed up the Network Manager based OpenVPN GUI as it does no longer properly supply the underlying daemon with the passkey correctly.
Running OpenVPN from the command line now asks for the password three times as seen below:
Tue May 20 19:37:12 2008 /usr/sbin/openssl-vulnkey -q /home/user/openvpn/key.pem
Enter pass phrase for /home/user/openvpn/key.pem:
Enter pass phrase for /home/user/openvpn/key.pem:
Enter Private Key Password:
There is a incorrect but working workaround suggested at Ubuntu launchpad:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/230197/
It suggests replacing openssl-vulnkey that is intended for checking x509 certificates with openvpn-vulnkey used for checking OpenVPN shared static keys. Replacing openssl-vulnkey with /bin/true works just as good as the suggested workaround at launchpad but obviously removes the intended check for blacklisted keys as well.
So check your keys using openssl-vulnkey, replace any keys needing replacing, make a backup of openssl-vulnkey and replace it with /bin/true TEMPORARLY. If your interested in monitoring the activity of the bug, become a subscriber at the link above. If not wait for the security update and make sure to apply it ones it's released.