nassh: add IDNA support |
||
Issue descriptiontoday if you try to use an IDN, it fails. we end up just trying to connect to a hostname using the encoded bytes. for example, 日本.com will try \346\227\245\346\234\254.com when it should have used punycode to connect to xn--wgv71a.example.com. seems like we should be able to import this guy: https://github.com/bestiejs/punycode.js license is MIT
,
May 10 2017
forgot to link to this bug in the last CL: https://chromium-review.googlesource.com/495354 this will be part of 0.8.36.4+ |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, May 9 2017