From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10216] package/x11r7/mcookie/mcookie.c:207: bad size ?
Date: Tue, 26 Sep 2017 10:36:41 +0000 [thread overview]
Message-ID: <bug-10216-163-bmwKL5L6zv@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10216-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10216
--- Comment #2 from Peter Korsgaard <jacmet@uclibc.org> ---
FYI, this specific issue was fixed upstream (util-linux) back in 2009:
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/lib/md5.c?id=6596057175c6ed342dc20e85eae8a42eb29b629f
I'll fix up our embedded mcookie.c copy as well for 2017.02.7 and 2017.08.1.
Moving forward, it indeed makes more sense to use the util-linux version.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-09-26 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 20:26 [Buildroot] [Bug 10216] New: package/x11r7/mcookie/mcookie.c:207: bad size ? bugzilla at busybox.net
2017-09-25 19:03 ` [Buildroot] [Bug 10216] " bugzilla at busybox.net
2017-09-26 10:36 ` bugzilla at busybox.net [this message]
2018-01-10 21:30 ` bugzilla at busybox.net
2018-01-12 18:59 ` bugzilla at busybox.net
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=bug-10216-163-bmwKL5L6zv@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.