Your message dated Fri, 19 Jun 2026 14:49:12 +0000
with message-id <[email protected]>
and subject line Bug#1119636: fixed in yersinia 0.8.2-2.4
has caused the Debian Bug report #1119636,
regarding yersinia: 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.)
--
1119636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119636
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: yersinia
Version: 0.8.2-2.2+b1
User: [email protected]
Usertags: hardening-buildflags
yersinia 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 yersinia 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
yersinia, 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: yersinia
Source-Version: 0.8.2-2.4
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
yersinia, 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.
Andreas Tille <[email protected]> (supplier of updated yersinia 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, 09 Jun 2026 15:50:54 +0200
Source: yersinia
Architecture: source
Version: 0.8.2-2.4
Distribution: unstable
Urgency: medium
Maintainer: Noël Köthe <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1119636
Changes:
yersinia (0.8.2-2.4) unstable; urgency=medium
.
* Non-maintainer upload.
* Move package to Salsa
* d/watch: version=5
* d/copyright: DEP5
* Build-Depends: libncurses5-dev => libncurses-dev
* debhelper-compat (= 13)
* Short dh
Closes: #1119636
* Enable hardening options
* Standards-Version: 4.7.4 (Removed Priority field)
* Rely on pre-initialized dpkg-architecture variables.
* Refer to specific version of license GPL-2+.
* Trim trailing whitespace.
* Add d/u/metadata
Checksums-Sha1:
19fed591b527f7e7d5d014a5a2bf9bec4c7dd87e 1923 yersinia_0.8.2-2.4.dsc
2df7d93708421a1027f26a284a9b6e3404f5de99 5960 yersinia_0.8.2-2.4.debian.tar.xz
a12036225856a164ef0f6e5eb0a730fafd534c90 7484
yersinia_0.8.2-2.4_amd64.buildinfo
Checksums-Sha256:
ac9f57cb48dec176b7ec9ad133361a6622ebcc86753635579aa9ff2bdfe6ae9c 1923
yersinia_0.8.2-2.4.dsc
328214a1f97f2247db096cd9e53f62047da7e0dd860fe8265fc21130261904a0 5960
yersinia_0.8.2-2.4.debian.tar.xz
e162c2c88e5b59ceb176e2bea2ef159f997e2ea06aaa25f646c4dd6a3ae44054 7484
yersinia_0.8.2-2.4_amd64.buildinfo
Files:
5de464e74a2a8dd0b92e1cf4294bf229 1923 admin optional yersinia_0.8.2-2.4.dsc
2e9801f293a4e100c779328c4da9d123 5960 admin optional
yersinia_0.8.2-2.4.debian.tar.xz
fe210518bfe65232bccad0eb79253015 7484 admin optional
yersinia_0.8.2-2.4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmooHFMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGfIg/+PgdFE1asoB+JOzvesoDGhaJ1ct/ZzvaN
Wh8Nfrxz/WxlyhTQFio2072xpSjrUl0DR6oWPzBa76AEVELamYFy6WI4edWhJysw
YCEO2AnMieP8+igmRYRS+akDgCvKkA+Ke0ozCVHUK+c0/2SQ6uShXalwVAjf2aaT
YKJFlKJc+kzrwatEh54bpE3cvhMLNKWCsXv9WHaOh0zHs9Q5Mv3UbqeBol42ik3p
dGPdU3WDUkert7iN2fIa0T5DJrNYxGty9aBXCJyeLLf/jBtEr5CVddyzzVu9Q95/
dNkKD6eHwCEgMpxlFwb8sgmmvB2U630OFHIWMVwDOrjGzXLPgP0svPYIS6+WVFhr
eQDVK6/gcTLth//isvcwY/dHjNidmF4YnTgYcvtCwQGX/mB+DqQvGu/N9Y/rfa/G
ouFMSQgCzL/ss27GchlTxZDnYY7oLdxkMyLxrsXhSmuFiMycEu+xqbWodqYA7e10
oKrGoBV1IRGx3UkxHdbqsXnP1TTMUOuZ8mM0Z2O/aK+/DkF47aOjumDriWDxPaxu
wpyYa8w+gB7wFdepPBojpcnJEi25zl+UfYDL8DrsU05M1CKwuwJnu7uq2zDDIKwa
FhxXWpsmB1OYHjO3lFjxlyKrnxw8GWAeJttEp6EeSVkr/G+uZS5DOOhCCXR3MV6K
EMF3Rfvd4KY=
=TeZc
-----END PGP SIGNATURE-----
pgpWDfNp7TQsu.pgp
Description: PGP signature
--- End Message ---
