dropbear: fix build with non-SSP capable toolchain
By default, Dropbear's configure script enables hardening
flags. Unfortunately, the check for SSP only uses AC_COMPILE_IFELSE(),
and therefore doesn't properly test for the availability of libssp,
visible only at link time.
In addition, Buildroot passes its own hardening flags, depending on
various global options. So, we simply disable hardening flags in
Dropbear.
This fixes a build failure with non-SSP capable toolchains happening
since the bump to 2018.76.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
(cherry picked from commit b0aafef619
)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
parent
e7fc3403bb
commit
dccaff8e82
@ -12,6 +12,11 @@ DROPBEAR_LICENSE_FILES = LICENSE
|
||||
DROPBEAR_TARGET_BINS = dropbearkey dropbearconvert scp
|
||||
DROPBEAR_PROGRAMS = dropbear $(DROPBEAR_TARGET_BINS)
|
||||
|
||||
# Disable hardening flags added by dropbear configure.ac, and let
|
||||
# Buildroot add them when the relevant options are enabled. This
|
||||
# prevents dropbear from using SSP support when not available.
|
||||
DROPBEAR_CONF_OPTS = --disable-harden
|
||||
|
||||
ifeq ($(BR2_PACKAGE_DROPBEAR_CLIENT),y)
|
||||
# Build dbclient, and create a convenience symlink named ssh
|
||||
DROPBEAR_PROGRAMS += dbclient
|
||||
|
Loading…
Reference in New Issue
Block a user