Your message dated Sat, 16 May 2026 17:20:03 +0000
with message-id <[email protected]>
and subject line Bug#1119573: fixed in ssocr 2.25.1-2
has caused the Debian Bug report #1119573,
regarding ssocr: 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.)
--
1119573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119573
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ssocr
Version: 2.25.0-1
User: [email protected]
Usertags: hardening-buildflags
ssocr 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 ssocr 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
ssocr, 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: ssocr
Source-Version: 2.25.1-2
Done: Alex Myczko <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ssocr, 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.
Alex Myczko <[email protected]> (supplier of updated ssocr 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, 06 May 2026 10:47:37 +0000
Source: ssocr
Architecture: source
Version: 2.25.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alex Myczko <[email protected]>
Changed-By: Alex Myczko <[email protected]>
Closes: 1119573
Changes:
ssocr (2.25.1-2) unstable; urgency=medium
.
* Fix default build flags. (Closes: #1119573)
Checksums-Sha1:
0ede5cd852a06b06420a625a701f740cf819d140 1902 ssocr_2.25.1-2.dsc
de2fa44b278960d6f74405fd6ae78263744b5825 3216 ssocr_2.25.1-2.debian.tar.xz
e80a92bb56ed71127ffb1b3aa7a949762c2589a1 12847 ssocr_2.25.1-2_source.buildinfo
Checksums-Sha256:
e169ebc287ad54dbffe32fae637d00eec5e25a1c434acd81caaf5c755eeec28a 1902
ssocr_2.25.1-2.dsc
50ccbbb5729a2f09b0e952369d3a80e348898dbb5cc609bdd55c00ddff292fc7 3216
ssocr_2.25.1-2.debian.tar.xz
234f2bbc157a00aef6b8248f92a51c080f3dfc12a1976c04d1125d334fe5c6ed 12847
ssocr_2.25.1-2_source.buildinfo
Files:
b9d6175215b46536dfce8d61a95b2ab6 1902 graphics optional ssocr_2.25.1-2.dsc
84a0490c1440ceb50285eddb3bd4423a 3216 graphics optional
ssocr_2.25.1-2.debian.tar.xz
7a0e74b9cde679e96edbb89a09649a3f 12847 graphics optional
ssocr_2.25.1-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmoIoXUPHHRhckBkZWJp
YW4ub3JnAAoJEBFoUrzfdRXABuIP+wYRI6J18D6cjie854//CZ8C0mA0cojzal2E
6vvNXrfogksWm4/qnx5VIcUdD7xkio8KyGWSidaWTcF4o9TPBds7YGMzzM0ohLuX
g0KsHxE5FtaCRIgpjjXMjkimlY6luTfByHUERdg6Q/hZ4dGVzdZzfMkmAdY3uj62
NggFZopf5nOlKQ1yCOu/8dDhEQ8HM4UMYMZyslnq3jAFfB/WM/bnwOuiWsa/xRDx
bGp2OdeZZh3V3G4kCQ6h3ZhDIwo4WGhyGLhZWeZBjnVbfCJR6xkLAD9g8eGRKUC9
WW+AbuVjHf/Gqwju2cC43eXUV2KEqsu7WWmzRxfzU7CnG0gARNprwNZmKGt3jBbz
X4MehSHY+ayV3TawwbUA316WXmWsSIJMfvveLgFmmtAZcpulFbJKNyqDygoMChOt
HwPLYZ2sEQnjqM9YFUNpN3ghzPboNdnq/9miTyMkRfdlnmsDWL+79Go9jywhkAUc
uIT8hZ7NBjMv+SBBR62x6190SL/zE+YzECWnz9TkEN6iVNh+cj78LsT/ndG5U0UL
vXB+2+zJhdB4T1BtFXrgFNwO2OQBoggrkEYW2jCadR5Ye7O+Z2jSXVtocuK8Nsrp
1xOV0fiIEN8nPQXFiefiokCA1j3M1ub8HJhCqxF/w6qDbBDwxE5jI/EcjImv3AYe
JHbELn3S
=IREf
-----END PGP SIGNATURE-----
pgpmZo_MGhcS5.pgp
Description: PGP signature
--- End Message ---
