Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2,1/1] pppd: fix build with glibc 2.28
Date: Thu, 1 Nov 2018 14:32:16 +0100	[thread overview]
Message-ID: <20181101143216.7099e6e8@windsurf> (raw)
In-Reply-To: <20181031102825.30422-1-fontaine.fabrice@gmail.com>

Hello,

On Wed, 31 Oct 2018 11:28:25 +0100, Fabrice Fontaine wrote:
> Since glibc 2.28
> (https://savannah.gnu.org/forum/forum.php?forum_id=9205), 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 retrieve an upstream patch to use openssl instead of these functions
> and a new patch to remove the unsafe header/library path
> '-I/usr/include/openssl'
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/c13ca8b8afa8de700caf8cd2fa1812b8552b3f4a
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2:
>  - Add Signed-off-by and upstream link for upstream patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-11-01 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 10:28 [Buildroot] [PATCH v2,1/1] pppd: fix build with glibc 2.28 Fabrice Fontaine
2018-11-01 13:32 ` Thomas Petazzoni [this message]

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=20181101143216.7099e6e8@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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