From: Selva Nair
Check the config file location and command line options first
and membership in OpenVPNAdministrators group after that as
the latter could be a slow process for active directory users.
When connection to domain controllers is poor or unavailable, checking
the group membership is
Hi Antonio,Gert is correct, our compatibility layer is a set of functions in
wolfSSL which emulate the OpenSSL API. These functions are then macro defined
to have the same names as the OpenSSL functions. The configure script needs to
know where the wolfSSL headers are and that it should link aga
Hi Juliusz,
if wolfssl support is being introduced by means of the openssl
compatibility layer, why do people need to configure OpenVPN with
"./configure --with-crypto-library=wolfssl", rather than just using
openssl and specifying a different path for headers/libraries?
Isn't the compat layer in
Hi,
On 09/02/2020 10:50, Gert Doering wrote:
> Hi,
>
> On Sun, Feb 09, 2020 at 10:44:48AM +0100, Antonio Quartulli wrote:
>> if wolfssl support is being introduced by means of the openssl
>> compatibility layer, why do people need to configure OpenVPN with
>> "./configure --with-crypto-library=wo
Hi,
On Sun, Feb 09, 2020 at 10:44:48AM +0100, Antonio Quartulli wrote:
> if wolfssl support is being introduced by means of the openssl
> compatibility layer, why do people need to configure OpenVPN with
> "./configure --with-crypto-library=wolfssl", rather than just using
> openssl and specifying
Hi Gert,
thank you for your comments. My intention was not to add a second cipher
line in the sample config file. I added "cipher AES-256-CBC" to an
earlier version of OpenVPN when there was no cipher specified in the
loopback-client and loopback-server files. After rebasing my commit onto
ma
