From: ng0 <ng0@libertad.pw>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Fwd: [curl] Re: configure: --with-libidn or --with-libidn2?
Date: Mon, 26 Dec 2016 17:10:50 +0000 [thread overview]
Message-ID: <87k2amty3p.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161226170056.GB9351@jasmine>
Leo Famulari <leo@famulari.name> writes:
> On Mon, Dec 26, 2016 at 01:59:22PM +0000, ng0 wrote:
>> It seems as if curl can be build with libidn2 now and they have
>> addressed the bug which existed for a while. I will check with
>> upstream and send in a fix for our curl package once I am sure
>> that the old bug has been fixed.
>
> Which bug?
>
> In November 2016, the curl maintainers asked packagers to not link curl
> with libidn or libidn2 at all, due to security issues:
>
> https://curl.haxx.se/mail/lib-2016-11/0033.html
>
Which has since then be fixed and in a recent (not in 7.52.1
included) commit the --with-libidn2 option has been added.
My understanding of libidn2 is that there were problems with some
usecases. For example a domain name like bäcker.de would give
problems to applications such as curl. Of course this was months
ago, and I would not trust my memory on this.
--
♥Ⓐ ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org
next prev parent reply other threads:[~2016-12-26 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 13:59 Fwd: [curl] Re: configure: --with-libidn or --with-libidn2? ng0
2016-12-26 14:19 ` ng0
2016-12-26 17:00 ` Leo Famulari
2016-12-26 17:10 ` ng0 [this message]
2016-12-26 17:35 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2amty3p.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).