References: <1516423974-22159-1-git-send-email-selva.nair@...277...> <201801251118.w0PBIn3d083413@...2054...> From: Steffan Karger Message-ID: <857ede9e-80ec-fab5-7c57-00873ed2e33f@...1435...> Date: Thu, 25 Jan 2018 18:00:44 +0100 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Subject: Re: [Openvpn-devel] [PATCH applied] Re: TLS v1.2 support for cryptoapicert -- RSA only List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: openvpn-devel@lists.sourceforge.net On 25-01-18 16:14, Selva Nair wrote: > A more useful thing to do is to catch the case of user setting min = > 1.2 (as in trac 977) and we changing max to 1.1 when key is in a > legacy key store. That would cause a handshake failure with a cryptic > error. Better to catch early with a helpful warning. Will consider a > patch for that and trim down the above log message at that time. Ah, I actually have a patch ready for that in my local master branch, but still needed to send it out. So if you haven't started yet, I can send that out to the list. Otherwise I'll happily discard mine :) -Steffan