Hi,
On 16/04/2020 17:26, Arne Schwabe wrote:
> Signed-off-by: Arne Schwabe
Patch looks good and does what it says.
I tested the parser to make sure it still parses the ciphers as
expected, and it does:
./openvpn --tls-cipher
TLS-RSA-PSK-WITH-CHACHA20-POLY1305-SHA256:TLS-RSA-PSK-WITH-AES-256-GC
Hi,
On Fri, Apr 17, 2020 at 9:22 PM Antonio Quartulli wrote:
>
> Hi,
>
> On 18/04/2020 00:41, Jonathan K. Bullard wrote:
> > Hi,
> >
> > On Fri, Apr 17, 2020 at 5:35 PM Gert Doering wrote:
> >>
> >> ... the new subkeys are just a few weeks old, so we need to publish
> >> a new key bundle with th
> Hi,
>
> On Fri, Apr 17, 2020 at 5:35 PM Gert Doering wrote:
>>
>> ... the new subkeys are just a few weeks old, so we need to publish
>> a new key bundle with the new subkeys.
>
> So until a new security-keys-2020.asc (or whatever you will call it)
> is published on the OpenVPN website, I can't
Hello!
We use patch from https://community.openvpn.net/openvpn/ticket/845 for
several years,
it is still interesting for us and allows to set cipher per client in ccd.
Unfortunately, 2.4.9 makes this patch incompatible.
Is it possible to update this patch to 2.4.9 ? Unfortunately I have
The logic is to treat EEXIST as non-error because it means that the
address/soute we wanted to install already exists, therefore we can
move on and not fail.
However, this logic is currently based on checking errno == EEXIST.
This is wrong, because sitnl_send() does not set errno, but returns the
Hi,
On Fri, Apr 17, 2020 at 03:54:00PM -0400, David Kincade wrote:
> I work for a small company and I am running OpenVPN Connect Client 3.1.0
> (890) on Mac OS Catalina 10.15.4. I have the following issue:
>
> When I connect to the company VPN (OpenVPN but I don't know version info) I
> lose my D
