Your message dated Tue, 23 Jun 2026 15:34:38 +0000
with message-id <[email protected]>
and subject line Bug#1119575: fixed in steghide 0.5.1+git20240220-2
has caused the Debian Bug report #1119575,
regarding steghide: please build using the default build flags
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1119575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119575
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: steghide
Version: 0.5.1-15
User: [email protected]
Usertags: hardening-buildflags
steghide is not currently using the default build flags set by
dpkg-buildflags(1).
The default flags are chosen for multiple reasons including security,
performance, reproducibility, adherence to standards, and error handling.
Please make sure that steghide builds using the default build flags. blhc(1p)
and hardening-check(1) can be used to confirm that the issue is fixed.
In the general case, packages honoring CFLAGS, LDFLAGS, and other
similar environment variables get the default build flags for free
without the need for any work on the maintainer side. In the case of
steghide, the flags are either ignored or overridden.
The most common reasons for this are:
Hand-written Makefiles
----------------------
Some upstream Makefiles either override the values of variables such as
CFLAGS and similar or do not use them at all. See:
https://wiki.debian.org/HardeningWalkthrough#Handwritten_Makefiles
Misconfigured build systems
---------------------------
If the upstream code uses autotools, CMake, or other popular build
systems, it usually requires no further modifications. If might however
be that some variables are hardcoded in some way.
In this CMake snippet, the value of CXXFLAGS is overwritten with "-O2":
set(CMAKE_CXX_FLAGS "-O2")
If the intention is to append to CXXFLAGS, one should use the following
instead:
set(CMAKE_CXX_FLAGS "-O2 ${CMAKE_CXX_FLAGS}")
See #655870 for a similar autotools example.
Very old debhelper usage
------------------------
Packages not using dh(1), or those using a debhelper compatibility level
less than 9, need to manually include /usr/share/dpkg/buildflags.mk in
order for the dpkg-buildflags variables to be set:
https://wiki.debian.org/Hardening#dpkg-buildflags
Flags hardcoded in debian/rules (either voluntarily or not)
-----------------------------------------------------------
Some packages voluntarily hardcode the values of CFLAGS and friends in
debian/rules, ignoring the defaults set by dpkg-buildflags(1).
Others attempt to append to the variables, but end up accidentally
overriding the defaults:
#!/usr/bin/make -f
export CFLAGS += -pipe -fPIC -Wall
%:
dh $@
Debhelper only sets CFLAGS if it is not set yet. In the example above,
when dh is invoked the value of CFLAGS is "-pipe -fPIC -Wall", hence the
hardened defaults are not used. The right way to append to CFLAGS is
using DEB_CFLAGS_MAINT_APPEND instead, as documented in
dpkg-buildflags(1).
For a detailed analysis of this issue, see:
https://people.debian.org/~ema/nocflags_paper.pdf (eprint: hal-05334704)
--- End Message ---
--- Begin Message ---
Source: steghide
Source-Version: 0.5.1+git20240220-2
Done: Sven Geuer <[email protected]>
We believe that the bug you reported is fixed in the latest version of
steghide, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sven Geuer <[email protected]> (supplier of updated steghide package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 23 Jun 2026 17:12:29 +0200
Source: steghide
Architecture: source
Version: 0.5.1+git20240220-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <[email protected]>
Changed-By: Sven Geuer <[email protected]>
Closes: 1119575 1125714
Changes:
steghide (0.5.1+git20240220-2) unstable; urgency=medium
.
* Team upload.
.
[ Sven Geuer ]
* d/p/*: Add patch to keep CXXFLAGS untouched by upstreams build system.
(Closes: #1119575)
* d/p/*: Add patch fixing stack-based buffer overflow in Embedder.cc.
(Closes: #1125714)
* d/s/lintian-overrides: Removed, not needed anymore.
.
[ Alexandre Detiste ]
* drop "Rules-Requires-Root: binary-targets", not needed anymore
Checksums-Sha1:
b5a867cbf5c0804fc56e70b74718e585c7a8a87e 2191 steghide_0.5.1+git20240220-2.dsc
bed1bc8c89e0e1e84e52994f71d04c83ad2434fd 14492
steghide_0.5.1+git20240220-2.debian.tar.xz
50689acba03f6f90fd5ef86f08c89b5b74cf0c7e 6706
steghide_0.5.1+git20240220-2_amd64.buildinfo
Checksums-Sha256:
d8c9b34f0dc5bcd19e574bf6da17ad130132d9835236f9d58f2d704bda4306e4 2191
steghide_0.5.1+git20240220-2.dsc
63c7b43b66773201b653b0269cb1eb84f158da6f79a6a53d885ee21b9e95cbfb 14492
steghide_0.5.1+git20240220-2.debian.tar.xz
588c24bf517878235550514e8f0b2c6a5f17e6082905e05687ae4e29ed7cf7a9 6706
steghide_0.5.1+git20240220-2_amd64.buildinfo
Files:
3b93afabdb17a1758b859bd6edddbd05 2191 misc optional
steghide_0.5.1+git20240220-2.dsc
e6d2f4204290d8f8b89a136004da1b70 14492 misc optional
steghide_0.5.1+git20240220-2.debian.tar.xz
56090245b12de7468dea7fabca0a199f 6706 misc optional
steghide_0.5.1+git20240220-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEEPfXoqkP8n9/QhvGVrfUO2vit1YUFAmo6o7APHHNnZUBkZWJp
YW4ub3JnAAoJEK31Dtr4rdWFCDcP/2TTaUg9t6MEotX3OK3HoR27PCj9KKLAuU6F
WB7OKVRB9ZsfIekbBGZ7xlX3sOwfLerUjc3KGSKwbrJhyxSLGzyF9GR+kzXaZRWS
koTwvEyJw1SHDr6gjthhFnDlo5/qwVINZJKEvBwJQnCuWLNtq3RfgBeU3HPdbzgo
QK/bg7ny6HLEhCBp2vuDLLeGbR8sn8vRyMRubeIULbtfnfaH0bSE+mHj7C004wKQ
jZEMgqbnxqhpOWZG7dLzlxF9FRvwhraT/wSlMzWovRT2zlMoFet0apaiumWHDL1d
wgUPtifBL5hV8aVprotUwEELjlTwMaNTtSwpxnYEOZGc6vHCVYGsG8p3P2l7Vo8Z
Dd+wMN1m9ymxWr+4Z3HotYw8bYqZmBR/kjcgrsS9h4t7gJ7gnvBHsVyTJW5xbdRy
epY/dIxBrrB6g2KUchpFQv9AMlDDrJJTXDOrHS/Cy/oYPEeqV26D1eIcE2akLGWw
oKxxQ6LqI9N9PbblaaP/LLnWh3/8DjIdkqxC8xrThOtY4p+v3PNykPQ8+FE6M/FB
G7Tq4by0w5dRlGqjFKaYwSmQxyKAEcKYQcKUQ59kDPyw8QGBr5JXMyDjAMxVJjOJ
4xqTDSEgWcfQUa6qIp5rIbQ+ffuO6cYLF0P5iQc41L37ufzZ5KBwUgBqDWJr5C/Z
gLhEMCee
=myDe
-----END PGP SIGNATURE-----
pgpwXAXYFOrJl.pgp
Description: PGP signature
--- End Message ---
