Whenever I've built customs with openssl on a prefix I do the following
upon configure for OVPN
export PKG_CONFIG_PATH=<your prefix>/lib/pkgconfig
export CPPFLAGS=-I<your prefix>include
export LDFLAGS=-L<your prefix>/lib
export PKG_CONFIG_PATH=<your prefix>/lib/pkgconfig
then a ./configure --prefix=<your prefix> yadda yadda...
Side note. I've been building for Padlock support for years but in most recent
build despite both openssl engines and openvpn show-engines
indicating padlock support, and the kernel indicating that it's found padlock
that OpenVPN complains about not being able to use padlock
when it runs.
I've not had a chance to look closely at this. One thread of discussion I
stumbled across was new trends toward not supporting
hardware accelerators (was in a OpenBSD list) and random gen support for fear
of hardware level backdoors.
Anyhow just my $0.02.
c
On 2014-05-06, 11:34 AM, Florent B wrote:
It makes no difference... always same errors...
On 05/06/2014 05:25 PM, Andy Wang wrote:
-----Original Message-----
From: Florent B [mailto:flor...@coppint.com]
Sent: May-06-14 10:55 AM
To: openvpn-users@lists.sourceforge.net
Subject: [Openvpn-users] Building from source with custom OpenSSL
Hi all,
I use Debian Wheezy amd64.
I have to use a custom version of OpenSSL because I need VIA Padlock.
So I downloaded version 1.0.1g in /usr/src/openssl-1.0.1g, compiled it and it seems to
work ("openssl engine padlock" works).
Now I have OpenVPN 2.3.4 in /usr/src/openvpn-2.3.4.
I do:
./configure --prefix=/usr --enable-password-save
OPENSSL_SSL_LIBS="-L/usr/src/openssl-1.0.1g/"
OPENSSL_SSL_CFLAGS="-I/usr/src/openssl-1.0.1g/include/openssl/"
OPENSSL_CRYPTO_LIBS="-L/usr/src/openssl-1.0.1g/"
OPENSSL_CRYPTO_CFLAGS="-I/usr/src/openssl-1.0.1g/include/openssl/
---------------------
in the file it says "openssl/x509v3.h" so try
OPENSSL_SSL_CFLAGS="-I/usr/src/openssl-1.0.1g/include" and
OPENSSL_CRYPTO_CFLAGS=""-I/usr/src/openssl-1.0.1g/include/"
andy
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users