Re: [Openvpn-devel] [ovpn-dco] Is cbc-hmac supported?

Hi Tony, On 26/11/2020 01:46, Tony He wrote: >>OpenSSL directly talks to the crypto engine via a proprietary interface >>that the FW/driver exposes to userspace. The *data* flow does not cross >>the linux kernel crypto API > > No, OpenSSL doesn't directly talk to the  crypto engine via a > propri

Re: [Openvpn-devel] [ovpn-dco] Is cbc-hmac supported?

>OpenSSL directly talks to the crypto engine via a proprietary interface >that the FW/driver exposes to userspace. The *data* flow does not cross >the linux kernel crypto API No, OpenSSL doesn't directly talk to the crypto engine via a proprietary interface that the FW/driver exposes to userspace

[Openvpn-devel] [PATCH applied] Re: Improve keys out of sync message

Acked-by: Gert Doering I have no test bed that will trigger this, but the change is not hard to understand (extend print_key_id() with a "auth=make_string(ks->authenticated)", append the result to the "TLS Error:" message. All other users of print_key_id() are all "just debug output", so the ne

[Openvpn-devel] [PATCH applied] Re: Add more documentation about our internal TLS functions

Acked-by: Gert Doering "This was an easy one" - documentation is good. Your patch has been applied to the master branch. commit 8292102b102ff62d6b7ed1254076b822cb113162 Author: Arne Schwabe Date: Fri Oct 23 14:02:54 2020 +0200 Add more documentation about our internal TLS functions

[Openvpn-devel] [PATCH applied] Re: Replace key_scan array of static points with inline function

Acked-by: Gert Doering Not sure if I ever understood these shortcuts (there are 3*2 keys in session[].keys[], but the shortcuts only reference [0][0], [0][1] and [2][1]) but from a "mechanically comparing before/after" point of view, the change looks sane. Plus, it passes client side tests, wi

[Openvpn-devel] Summary of the community meeting (25th November 2020)

Hi, Here's the summary of the IRC meeting. --- COMMUNITY MEETING Place: #openvpn-meeting on irc.freenode.net Date: Wed 25th November 2020 Time: 11:30 CET (10:30 UTC) Planned meeting topics for this meeting were here: Your local