Hi On Sat, Jan 20, 2018 at 09:05:50AM -0500, Selva Nair wrote: > If/when the TLS1.2+ support for cryptoapicert is ready for merge, is > it a candidate for 2.4? Technically its a new feature but considering > the "popular belief" that TLS1.1 needs to be shunned, and 2.5 is still > far away, its worth considering.. > > In that case this patch would need to be backported to 2.4, so good to > know what's the general consensus.
I would argue that TLS 1.2 is officially supported by 2.4, and as such it's a bug if cryptoapicert doesn't :-) Given that the changes are fairly well localized and will not affect other platforms, and are likely to not affect users that do not use cryptoapicert, I would tend to "make sure that all we offer works with TLS 1.2" -> include in 2.4 But I let Steffan or David overrule me here if they find the patch too intrusive. gert -- now what should I write here... Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
