Your message dated Sat, 31 Jan 2026 11:48:27 +0000
with message-id <[email protected]>
and subject line Bug#1119625: fixed in xkbind 2010.05.20-1.1
has caused the Debian Bug report #1119625,
regarding xkbind: 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.)
--
1119625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119625
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: xkbind
Version: 2010.05.20-1+b3
User: [email protected]
Usertags: hardening-buildflags
xkbind 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 xkbind 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
xkbind, 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: xkbind
Source-Version: 2010.05.20-1.1
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
xkbind, 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 xkbind 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: Wed, 21 Jan 2026 11:50:10 +0100
Source: xkbind
Architecture: source
Version: 2010.05.20-1.1
Distribution: unstable
Urgency: medium
Maintainer: Stanislav Maslovski <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1119625 1120993
Changes:
xkbind (2010.05.20-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Maintain in Debian team space
Closes: #1120993
* d/watch: version=5
* Standards-Version: 4.7.3
* debhelper-compat 13 (routine-update)
Closes: #1119625
* Reorder sequence of d/control fields by cme (routine-update)
* Use secure URI in Homepage field.
* Lintian-overrides for national-encoding
* d/rules: Hardening
* d/copyright:
- DEP5
- Secure URI in Source
Checksums-Sha1:
22ca5e01d5e63f6049720378f00c94ceecb87a3c 1893 xkbind_2010.05.20-1.1.dsc
b51747bd342d6e42ad664745f2c4ef228c2441da 3052
xkbind_2010.05.20-1.1.debian.tar.xz
eccadd52a7d0d4444129089c2f4b2dd0526f81b7 6381
xkbind_2010.05.20-1.1_amd64.buildinfo
Checksums-Sha256:
711536f3e2f4691eac9394fd6d15fb9349577ff7eac3ae041b93574808c14e9c 1893
xkbind_2010.05.20-1.1.dsc
203768a4d0ac5b7ed03fc02f6a6ae24e0869c86b2b4c64d952da24569bdcd301 3052
xkbind_2010.05.20-1.1.debian.tar.xz
3d7b45c776a6d05e2eb330362e5d42833431102da456de717aef3667739b706d 6381
xkbind_2010.05.20-1.1_amd64.buildinfo
Files:
be42de17dff17251d9fc040964979366 1893 x11 optional xkbind_2010.05.20-1.1.dsc
45075c0615e136af317937d749437c6a 3052 x11 optional
xkbind_2010.05.20-1.1.debian.tar.xz
04963656be7cfd02f185a9a2cbd5d8f0 6381 x11 optional
xkbind_2010.05.20-1.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmlwsOsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH0mw//YsZn298saZT0Cq8sb6UZPHcE/YcdF/fJ
kQYZgWY5WzgCJIxpmJxXR5kSWG9VQJ6n8ayuj5GFAxNefmK9f9LbBmB0//Wt0sil
gbJlGaKYVnDl9B6xFdkgFvDE+sXKhMvaSN+9NV5sgIQ4Jer9YF7iBu9rJG5dyAsb
Owz80v7Tt8eBjK2aoWK8Qen7yRSHJVOfSX8DUw1Vb48Jo8ZSOWHIYsPzlirLS/cM
YpDA3qcC46hNkNpYcGqnqzU1T/IsE1mtkTr66DK/M5nDKfuwc3g8gO50tp8hjrtv
cDvKr5JDfvZXnzyI1hbTV1QT7BCKHeejJsDnptJceKdM0t8vkMkTM9d55yrqGxTw
nYb7FL28+TnkZkQNOdfOQj7wgzTAAXNRL+4EQOfnpcyYqRR2rmNmvvU4ct9u2QIm
flrlYHkbbvdZWTH7vaH5/Zn1dn+TLWMhZEKDDjiAuucsAT+YejxYCOPtHudoFdol
9yuH/s8oGlsYclKim0tFdPVUOykpg1ZJ2ChdzEFi1QBaGNCqkW9Lq+h1+eNrc+mQ
smmGOakh3KFmOpcvSWCSkUyLFqIs9q+fBxf7kIxmLgAtjgvRhl04DhXxe/quD8X0
JlgciEMc2WLpI3aX6KqbQYw6mYEhcqUo/MkuXmNbJ5u0G6GT2qA40ESaUrlCHQqd
b1mKQu9Apt8=
=InBs
-----END PGP SIGNATURE-----
pgp8n7UPjH3mC.pgp
Description: PGP signature
--- End Message ---
