Message-ID: <1163b61c-bc64-586a-e8f8-33e6d3abcbe7@...1227...> Date: Thu, 28 Jul 2022 17:38:06 +0200 MIME-Version: 1.0 Content-Language: en-GB References: <20220728152012.18643-1-a@...2181...> From: Arne Schwabe In-Reply-To: <20220728152012.18643-1-a@...2181...> Subject: Re: [Openvpn-devel] [PATCH v3 09/25] dco: configure keys in DCO right after generating them List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: Antonio Quartulli , openvpn-devel@lists.sourceforge.net Am 28.07.22 um 17:20 schrieb Antonio Quartulli: > The ovpn-dco kernel module needs to be informed about the keys to be > used to encrypt/decrypt data traffic to/from a peer. > > Configure keys in DCO right afte they are generated by the SSL code, to > avoid keeping them in memory longer than needed. > > Signed-off-by: Antonio Quartulli > --- > > Changes from v2: > * re-enable explicit-exit-notification in every case > * add check to drop packet when attempting to send data packet and DCO > is enabled (print warning as well) > > Changes from v1: > * adapt to new member name dco_enabled > * invert if blocks and condition in init_key_contexts() [and use 'else'] > * fix comment for init_key_contexts() > * disable explicit-exit-notification in mutate_ce() when DCO is enabled Acked-By: Arne Schwabe