On Sat, Dec 30, 2017 at 2:28 AM, Antoine Pitrou wrote:
> On Fri, 29 Dec 2017 21:54:46 +0100
> Christian Heimes wrote:
>>
>> On the other hand ssl module is currently completely broken. It converts
>> hostnames from bytes to text with 'idna' codec in some places, but not
>> in all. The SSLSocket.s
On Sat, Dec 30, 2017 at 7:26 AM, Stephen J. Turnbull
wrote:
> Christian Heimes writes:
> > Questions:
> > - Is everybody OK with breaking backwards compatibility? The risk is
> > small. ASCII-only domains are not affected
>
> That's not quite true, as your German example shows. In some Orienta
Ethan Furman writes:
> Good point. So auto-generate a new __repr__ if:
>
> - one is not provided, and
> - existing __repr__ is either:
>- object.__repr__, or
>- a previous dataclass __repr__
-0.5 I'm with Guido here. Just use the simple rule that a new
__repr__ is generated unles
Christian Heimes writes:
> tl;dr
> This mail is about internationalized domain names and TLS/SSL. It
> doesn't concern you if you live in ASCII-land. Me and a couple of other
> developers like to change the ssl module in a backwards-incompatible way
> to fix IDN support for TLS/SSL.
Yes plea
ssl.match_hostname was added in Python 2.7.9, looks like Python 2 should be
fixed as well.
On Sat, Dec 30, 2017 at 3:50 PM Antoine Pitrou wrote:
>
> Thanks. So the change sounds ok to me.
>
> Regards
>
> Antoine.
>
>
> On Sat, 30 Dec 2017 14:34:04 +0100
> Christian Heimes wrote:
> > On 2017-12
Thanks. So the change sounds ok to me.
Regards
Antoine.
On Sat, 30 Dec 2017 14:34:04 +0100
Christian Heimes wrote:
> On 2017-12-30 11:28, Antoine Pitrou wrote:
> > On Fri, 29 Dec 2017 21:54:46 +0100
> > Christian Heimes wrote:
> >>
> >> On the other hand ssl module is currently completely
On 2017-12-30 13:19, Skip Montanaro wrote:
> Guido wrote:
>
> This being a security issue I think it's okay to break 3.6. might
> even backport to 3.5 if it's easy?
>
>
> Is it also a security issue with 2.x? If so, should a fix to 2.7 be
> contemplated?
IMO the IDNA encoding problem is
On 2017-12-30 11:28, Antoine Pitrou wrote:
> On Fri, 29 Dec 2017 21:54:46 +0100
> Christian Heimes wrote:
>>
>> On the other hand ssl module is currently completely broken. It converts
>> hostnames from bytes to text with 'idna' codec in some places, but not
>> in all. The SSLSocket.server_hostnam
I’m traveling until next week, and haven’t had time to read any of these
emails. I’ll look at them when I return.
--
Eric.
> On Dec 30, 2017, at 5:20 AM, Raymond Hettinger
> wrote:
>
>
>> On Dec 29, 2017, at 4:52 PM, Guido van Rossum wrote:
>>
>> I still think it should overrides anything
Guido wrote:
This being a security issue I think it's okay to break 3.6. might even
backport to 3.5 if it's easy?
Is it also a security issue with 2.x? If so, should a fix to 2.7 be
contemplated?
Skip
___
Python-Dev mailing list
Python-Dev@python.org
> On Dec 29, 2017, at 4:52 PM, Guido van Rossum wrote:
>
> I still think it should overrides anything that's just inherited but nothing
> that's defined in the class being decorated.
This has the virtue of being easy to explain, and it will help with debugging
by honoring the code proximate t
On Fri, 29 Dec 2017 21:54:46 +0100
Christian Heimes wrote:
>
> On the other hand ssl module is currently completely broken. It converts
> hostnames from bytes to text with 'idna' codec in some places, but not
> in all. The SSLSocket.server_hostname attribute and callback function
> SSLContext.set
12 matches
Mail list logo
