[issue17305] IDNA2008 encoding missing

Change by Марк Коренберг : -- nosy: +socketpair ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue17305] IDNA2008 encoding missing

Nathaniel Smith added the comment: The "obvious" solution would be to move the "idna" module into the stdlib, but someone would still have to work that out, and it's clearly not happening for 3.7. -- versions: +Python 3.8 -Python 3.7 ___ Python tra

[issue17305] IDNA2008 encoding missing

Christian Heimes added the comment: I lack the expertise and time to implement IDNA 2008 with UTS46 codec. I considered GNU libidn2, but the library requires two more helper libraries and LGPLv3 might be an issue for us. -- ___ Python tracker

[issue17305] IDNA2008 encoding missing

R. David Murray added the comment: What we need for this issue is someone volunteering to writing the code. Given how long it has already been, I don't think anyone already on the core team is going to pick it up. -- ___ Python tracker

[issue17305] IDNA2008 encoding missing

Christian Heimes added the comment: bpo-31399 has fixed hostname matching for IDNA 2003 compatible domain names. IDNA 2008 domain names with German ß are still broken, for example: UnicodeError: ('IDNA does not round-trip', b'xn--knigsgchen-b4a3dun', b'xn--knigsgsschen-lcb0w') -- __

[issue17305] IDNA2008 encoding missing

Christian Heimes added the comment: A fix will land in 3.7 and maybe get backported to 3.6. Stay tuned! -- ___ Python tracker ___ __

[issue17305] IDNA2008 encoding missing

Nathaniel Smith added the comment: Greg: That's bpo-28414. There's currently no motion towards builtin IDNA 2008 support (this bug), but I *think* in 3.7 the ssl module will be able to handle pre-encoded A-labels like that. I'm a little confused about the exact status right now but there's be

[issue17305] IDNA2008 encoding missing

Greg Lindahl added the comment: I am avoiding Python's built-in libraries as much as possible in my aiohttp-based crawler because of this issue, but I cannot open a connection to https://xn--ho-hia.de because there is an 'IDNA does not round-trip' raise in the python 3.6 library ssl.py code.

[issue17305] IDNA2008 encoding missing

Change by Greg Lindahl : -- nosy: +wumpus ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue17305] IDNA2008 encoding missing

Change by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue17305] IDNA2008 encoding missing

Changes by Nathaniel Smith : -- nosy: +njs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue17305] IDNA2008 encoding missing

Changes by Socob <206a8...@opayq.com>: -- nosy: +Socob ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue17305] IDNA2008 encoding missing

Christian Heimes added the comment: I reported the issue for curl, CVE-2016-8625 https://curl.haxx.se/docs/adv_20161102K.html -- ___ Python tracker ___ _

[issue17305] IDNA2008 encoding missing

Changes by Sam Whited : -- nosy: +SamWhited ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue17305] IDNA2008 encoding missing

Changes by Cory Benfield : -- nosy: +Lukasa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue17305] IDNA2008 encoding missing

Christian Heimes added the comment: I'm considering lack of IDNA 2008 a security issue for applications that perform DNS lookups and X.509 cert validation. Applications may end up connecting to the wrong machine and even validate the cert correctly. Wrong: >>> import socket >>> u'straße.de'.e

[issue17305] IDNA2008 encoding missing

Changes by Christian Heimes : -- assignee: christian.heimes -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17305] IDNA2008 encoding missing

Changes by Christian Heimes : -- assignee: -> christian.heimes components: +SSL priority: normal -> high versions: +Python 3.7 -Python 3.5 ___ Python tracker ___ ___

[issue17305] IDNA2008 encoding missing

Changes by Christian Heimes : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue17305] IDNA2008 encoding missing

Changes by Berker Peksag : -- nosy: +berker.peksag versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list maili

[issue17305] IDNA2008 encoding missing

Martin v. Löwis added the comment: I would propose this approach: 1. Python should implement both IDNA2008 and UTS#46, and keep IDNA2003 2. "idna" should become an alias for "idna2003". 3. The socket module and all other place that use the "idna" encoding should use "uts46" instead. 4. Pre-exis

[issue17305] IDNA2008 encoding missing

Derek Wilson added the comment: It is worth noting that the do exist some domains that have been registered in the past that work with IDNA2003 but not IDNA2008. There definitely needs to be IDNA2008 support, for my use case I need to attempt IDNA2008 and then fall back to IDNA2003. When supp

[issue17305] IDNA2008 encoding missing

Marten Lehmann added the comment: There's nice library called idna on PyPI doing idna2008: https://pypi.python.org/pypi/idna/0.1 I'd however prefer this standard encoding to be part of standard python. -- ___ Python tracker

[issue17305] IDNA2008 encoding missing

era added the comment: At least the following existing domain names are rejected by the current implementation, apparently because they are not IDNA2003-compatible. XNNNC9BXA1KSA.COM XN--14-CUD4D3A.COM XN--YGB4AR5HPA.COM XN---14-00E9E9A.COM XN--MGB2DAM4BK.COM XN--6-ZHCPPA1B7A.COM XN--3-YMCC

[issue17305] IDNA2008 encoding missing

R. David Murray added the comment: Ah, excellent, that document looks like exactly what I was looking for. Now, when someone is going to get around to working on this, I don't know. (Note that the xrange/range change was made at the Python2/Python3 boundary, where we broke backward compatibili

[issue17305] IDNA2008 encoding missing

Marten Lehmann added the comment: I found an interesting link about this issue: http://www.unicode.org/faq/idn.html I also checked a domain name of a client that ends with 'straße.de': IE, Firefox and Chrome still use IDNA2003, Opera already does IDNA2008. In IDNA2008 a lot of characters aren

[issue17305] IDNA2008 encoding missing

R. David Murray added the comment: That doesn't sound like interoperability to me, that sounds like backward incompatibility :(. I hope you are right that it only affects people with hardcoded domain names, but that is still an issue. In any case, since this is a new feature it can only go in

[issue17305] IDNA2008 encoding missing

Marten Lehmann added the comment: IDNA2008 should be backwards compatible. I can try to explain it in a practical example: DENIC was the first registry that actually used IDNA2008 - at a time, where not even libidn2 officially included the changes required for it. This was mainly due to the p

[issue17305] IDNA2008 encoding missing

R. David Murray added the comment: Does this mean the differences are only in the canonicalization of unicode values? IDNA is a wire protocol, which means that an application can't know if it is being asked to decode an idna1 or idna2 string unless there's something in the protocol that tells

[issue17305] IDNA2008 encoding missing

Marten Lehmann added the comment: For the embedded Python examples, please prepend the following lines: from __future__ import unicode_literals name='müller.com' So regarding interoperability: Usually you only use one implementation in your code and hopefully the latest release, but in case so

[issue17305] IDNA2008 encoding missing

Marten Lehmann added the comment: At least from the GNU people, two separate projects exists for this matter: libidn, the original IDNA translation (http://www.gnu.org/software/libidn/) libidn2, the IDNA2008 translation (http://www.gnu.org/software/libidn/libidn2/manual/libidn2.html) Btw.: Doe

[issue17305] IDNA2008 encoding missing

R. David Murray added the comment: How are they handling interoperability? -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-

[issue17305] IDNA2008 encoding missing

New submission from Marten Lehmann: Since Python 2.3 the idna encoding is available for Internationalized Domain Names. But the current encoding doesn't work according to the latest version of the spec. There is a new IDNA2008 specification (RFCs 5890-5894). Although I'm not very deep into al