Timothe Litt ACM Distinguished Engineer -------------------------- This communication may not represent the ACM or my employer's views, if any, on the matters discussed.
On 09-Apr-14 08:25, openvpn-users-requ...@lists.sourceforge.net wrote:
Date: Wed, 09 Apr 2014 13:02:54 +0300
From: Samuli Sepp?nen<sam...@openvpn.net>
Subject: [Openvpn-users] Regarding pkcs11 support in our Debian/Ubuntu
packages
To:"openvpn-users@lists.sourceforge.net"
<openvpn-users@lists.sourceforge.net>,
"openvpn-de...@lists.sourceforge.net"
<openvpn-de...@lists.sourceforge.net>
Message-ID:<53451ace.1020...@openvpn.net>
Content-Type: text/plain; charset=ISO-8859-15
Hi all,
It OpenVPN 2.3.3 requires libpkcs11-helper 1.11 or newer. What this
means is that unless I patch the OpenVPN sources I won't be able to
provide Debian/Ubuntu packages with pkcs11 support except for Ubuntu
14.04 which has 1.11 in default repos.
So, is anyone using pkcs11 with the Debian packages I've provided? If
not, I will simply remove pkcs11 support and be done with it. I could
patch the openvpn sources to allow an older libpkcs11, but I'm not sure
if that would cause problems elsewhere.
-- Samuli Sepp?nen Community Manager OpenVPN Technologies, Inc irc
freenode net: mattock
I have not yet used pkcs11, but it is on my list to switch to tokens once some other issues are resolved.
I use debian on RPI. Currently a custom build, but I hope to switch back to the packages once they catch up to git (+ a not-yet-developed bugfix).
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
