From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [SECURITY] libidn - locale specific error in test suite
Date: Mon, 09 Jan 2017 14:26:00 -0000 [thread overview]
Message-ID: <20170109142640.GC843@calimero.vinschen.de> (raw)
In-Reply-To: <20381568-c93e-1517-0f3d-579a5e6ac3fa@volkerzell.de>
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
On Jan 3 11:53, Dr. Volker Zell wrote:
> On 29.12.2016 21:49, Yaakov Selkowitz wrote:
> > On 2016-09-30 01:43, Dr. Volker Zell wrote:
> > > > > > > > Yaakov Selkowitz writes:
> > >
> > > > Dr. Volker,
> > > > Several security vulnerabilities have been announced for
> > > libidn, which are fixed
> > > > in 1.33:
> > >
> > > >
> > > https://lists.gnu.org/archive/html/help-libidn/2016-07/msg00009.html
> > >
> > > Noted (and also your other mails), will work on it as soon as real
> > > work permits.
> >
> > Ping?
> >
>
> Hi
>
> Just tried packaging libidn-1.33 and found a locale specific error in the
> test suite (Which was working fine with my latest build). When running under
> strace I get:
> [...]
> : 37 4387 [main] test-localename 11148 write: 1 = write(2, 0x1004060B9,
> 1)
> 183 32 4419 [main] test-localename 11148 write: 3 = write(2,
> 0xFFFFC9F1, 3)
> : assertion ' 30 4449 [main] test-localename 11148 write: 13 = write(2,
> 0x1004060BC, 13)
> strcmp (name, "fr_FR.UTF-8") == 0 30 4479 [main] test-localename 11148
> write: 33 = write(2, 0x100406168, 33)
> ' failed
> [...]
>
> The source code can be found in the file (after unpacking of
> https://ftp.gnu.org/gnu/libidn/libidn-1.33.tar.gz)
>
> o .../libidn-1.33-1.x86_64/src/libidn-1.33/lib/gltests/test-localename.c
Do you have a self-contained testcase, by any chance?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-09 14:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 15:18 [SECURITY] libidn Yaakov Selkowitz
2016-09-30 6:44 ` Dr. Volker Zell
2016-12-29 20:49 ` Yaakov Selkowitz
2017-01-03 10:54 ` [SECURITY] libidn - locale specific error in test suite Dr. Volker Zell
2017-01-09 14:26 ` Corinna Vinschen [this message]
2017-01-18 12:13 ` Dr. Volker Zell
2017-01-18 15:24 ` Eric Blake
2017-01-19 10:39 ` Corinna Vinschen
2017-01-19 17:40 ` Eric Blake
2017-01-19 18:19 ` Corinna Vinschen
2017-01-19 20:17 ` Eric Blake
2017-01-19 21:02 ` Corinna Vinschen
2017-01-19 21:17 ` Eric Blake
2017-01-20 8:36 ` Corinna Vinschen
2017-01-19 20:34 ` Eric Blake
2017-01-19 20:43 ` Yaakov Selkowitz
2017-02-22 18:58 ` Yaakov Selkowitz
2017-03-10 22:01 ` Yaakov Selkowitz
2017-03-24 19:00 ` Yaakov Selkowitz
2017-05-03 21:38 ` Yaakov Selkowitz
2017-03-10 22:02 ` Yaakov Selkowitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170109142640.GC843@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/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.
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).