Re: libidn2 support

[Simon Josefsson]

Hi again.  I have added you now.  There is no real work going on with
libidn2, but Hanno Böck said he may have found more
security vulnerabilities, so it would be nice to be able to do a quick
security release if needed.  Therefor, it appears preferrable to push
your stuff to a branch meanwhile.  I'm happy to review when it is on a
branch, and hopefully we can make test releases from the branch too.

/Simon

> Hi Simon,
> 
> thanks for your offer !
> 
> I would be happy to push my changes.
> There is still time to test/discuss until the next release, I guess.
> Are you ok, if I push to master or would you like to have a separate
> branch ?
> 
> My name on Gitlab (and elsewhere) is rockdaboot.
> 
> Regards, Tim
> 
> 
> On Thursday, December 1, 2016 2:39:55 PM CET Simon Josefsson wrote:
> > Hi Tim.  Thanks, this is really cool.  Do you want commit access to
> > libidn2 so you can push this?  What's your gitlab username?  I have
> > limited time and don't want to be in your way for this to happen.
> > I'm happy to do review, but can't promise when.
> > 
> > /Simon
> > 
> > tis 2016-11-29 klockan 22:23 +0100 skrev Tim Rühsen:
> > > On Mittwoch, 2. November 2016 10:04:19 CET Daniel Stenberg wrote:
> > > > On Wed, 2 Nov 2016, Simon Josefsson wrote:
> > > > > Switching from IDNA2003 to IDNA2008 requires thought.  They
> > > > > are not compatible, and IDNA2008 requires pre-processing
> > > > > (e.g., UTS #46 [1]) to
> > > > > be usable in practice.  Libidn2 does not implement any
> > > > > pre-processing, it is a pure IDNA2008 implementation.
> > > > > 
> > > > > [1] http://www.unicode.org/reports/tr46/
> > > > 
> > > > Thanks for this Simon. I wasn't aware.
> > > > 
> > > > Based on this, I suppose my recommendation is that people
> > > > simply switch off
> > > > IDN support in curl builds until further notice to stay safe.
> > > > The old way
> > > > was open for trickery and the new way is incomplete.
> > > 
> > > Please review and comment
> > > https://gitlab.com/rockdaboot/libidn2/tree/tr46 (It works for me
> > > ).
> > > 
> > > I would like to open a pull request to libidn2 soon.
> > > That code will be useful for any DNS clients resolving IDNs.
> > > 
> > > From my mail to help-libidn mailing list:
> > > 
> > > The code introduces new flags for the lookup functions
> > > IDN2_TRANSITIONAL and IDN2_NONTRANSITIONAL (mutual exclusive).
> > > 
> > > IDN2_TRANSITIONAL enables the TR46 transitional process.
> > > IDN2_NONTRANSITIONAL enables the TR46 non-transitional process.
> > > 
> > > Corresponding, the 'idn2' utility now has -T/--tr46t to enable
> > > transitional
> > > lookup and -N/--tr46nt to enable non-transitional lookup.
> > > 
> > > Example:
> > > $ src/idn2 -T faß.de
> > > fass.de
> > > 
> > > $ src/idn2 -N faß.de
> > > xn--fa-hia.de
> > > 
> > > To show the TR46 mapping (upper->lowercase) in work:
> > > $ src/idn2 Faß.de
> > > idn2: lookup: string contains a disallowed character
> > > 
> > > $ src/idn2 -T Faß.de
> > > fass.de
> > > 
> > > $ src/idn2 -N Faß.de
> > > xn--fa-hia.de
> > > 
> > > Regards, Tim
>

pgpK5ecySZ5Z4.pgp
Description: OpenPGP digital signatur