From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11331] Internal application no longer builds with latest GIT master
Date: Tue, 11 Sep 2018 09:39:20 +0000 [thread overview]
Message-ID: <bug-11331-163-e8GOqJglmN@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11331-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11331
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
This is a decision from glibc upstream, which removed those functions from
glibc 2.28. See
https://lists.gnu.org/archive/html/info-gnu/2018-08/msg00000.html, which says:
"""
* The obsolete functions encrypt, encrypt_r, setkey, setkey_r, cbc_crypt,
ecb_crypt, and des_setparity are no longer available to newly linked
binaries, and the headers <rpc/des_crypt.h> and <rpc/rpc_des.h> are no
longer installed. These functions encrypted and decrypted data with the
DES block cipher, which is no longer considered secure. Software that
still uses these functions should switch to a modern cryptography library,
such as libgcrypt.
"""
So, you should fix your application it seems. Buildroot is not going to revert
this change, unless you can convince glibc upstream developers to also revert
it, which I guess will be challenging.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-09-11 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 9:30 [Buildroot] [Bug 11331] New: Internal application no longer builds with latest GIT master bugzilla at busybox.net
2018-09-11 9:39 ` bugzilla at busybox.net [this message]
2018-09-11 9:53 ` [Buildroot] [Bug 11331] " 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-11331-163-e8GOqJglmN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox