-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
my mistake, v3.0.9 does use date for build-x-full.
However, if you could also test latest release 3.1.2
that would help.
Thanks
Richard
Sent with Proton Mail secure email.
--- Original Message ---
On Thursday, January 19th, 2023 at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
EasyRSA version 3.0.x 'build-x-full' does not use date.
You must be using version 3.1.x
Please check which version you are using.
Releases are available, please try latest:
https://github.com/OpenVPN/easy-rsa/releases
If the problem persists
I've discovered what may be a bug in easyrsa 3.0. When I try to
create new certificates with build-server-full or build-client-full,
I get these error messages:
Failed conversion of ``'' using format ``%b %d %T %Y %Z''
date: illegal time format
usage: date [-jnRu] [-d dst]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Ralf,
I experienced a very similar issue when testing a DCO server.
For me, the solution was to remove ALL compression settings from
the client CCD file and server conf, including what appear to be
compatible settings.
I don't understand the re
Hi,
(copying openvpn-devel, as Arne and Antonio are not reading -users)
On Wed, Jan 18, 2023 at 05:34:51PM +0100, Ralf Hildebrandt via Openvpn-users
wrote:
> You might have noticed our bug reports regarding capabilities && 2.6rc2.
> The whole point of it all was to test 2.6.x's DCO in our openvp
You might have noticed our bug reports regarding capabilities && 2.6rc2.
The whole point of it all was to test 2.6.x's DCO in our openvpn infrastructure
:)
Upgrades were made, kernel module were being compiled and modprobed,
the gateway's filesystem is cluttered with source packages and
hotfixed
