Message274892
| Author |
christian.heimes |
| Recipients |
Jim.Jewett, Lukasa, alex, christian.heimes, dstufft, georg.brandl, giampaolo.rodola, hynek, janssen, larry, python-dev, steve.dower |
| Date |
2016年09月07日.21:02:14 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<05cf320f-7736-b56b-4ff8-1653bf3ecef2@cheimes.de> |
| In-reply-to |
<1473217569.22.0.459984320183.issue27850@psf.upfronthosting.co.za> |
| Content |
On 2016年09月07日 05:06, Larry Hastings wrote:
>
> Larry Hastings added the comment:
>
>> FWIW the cipher list (at least the restricted ones for
>> ssl.create_default_context()) is explicitly documented
>> as being able to be changed at any time without prior deprecation
>
> Yes. To be specific: "The protocol, options, cipher and other settings may change to more restrictive values anytime without prior deprecation."
>
> https://docs.python.org/3/library/ssl.html#ssl.create_default_context
>
> I've seen no documentation suggesting that we can add new ciphers at any time.
ChaCha20 is part of the HIGH cipher set. That means the patch does not
*add* ChaCha20. It's already added by the HIGH rule. The patch rather
moves the cipher ChaCha20 Poly1305 suits in the right place.
Christian |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年09月07日 21:02:14 | christian.heimes | set | recipients:
+ christian.heimes, georg.brandl, janssen, larry, giampaolo.rodola, alex, python-dev, hynek, Jim.Jewett, steve.dower, dstufft, Lukasa |
| 2016年09月07日 21:02:14 | christian.heimes | link | issue27850 messages |
| 2016年09月07日 21:02:14 | christian.heimes | create |
|