On 12 January 2017 at 22:44, Cory Benfield <c...@lukasa.co.uk> wrote: > We can do that. > > I should note that MINIMUM_SUPPORTED and MAXIMUM_SUPPORTED are not intended > to be equal to SSLv2 and TLSv1_3, or indeed to any other value in this enum. > They are future-proofing tools that allow users to say “I want TLSv1 *or > higher*” without setting an upper bound on what “higher” means.
Cool, I wasn't sure how you intended to handle that, and supplying the values will make it explicit that those are really only useful in "version_range" and not anywhere else. Although at that point the question becomes whether or not they're offering any benefit beyond just using "None" in the appropriate location. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Security-SIG mailing list Security-SIG@python.org https://mail.python.org/mailman/listinfo/security-sig
