bacula not compiled with FORTIFY_SOURCE

This problem *should* already be fixed in the trunk, though I have never actually tried building and running it with fortify source.

We *strongly* recommend not to enable fortify source. Bacula is already well protected and has its own buffer overrun detection that in general detects most overrun problems earlier and better than glibc and produces a reasonable traceback in the process. If you do enable fortify source, we cannot exclude that you will encounter other such problems.

Yeah, this is mostly a place-holder bug so we can review the roll-out of fortify-source distro-wide. Thanks for looking into it! It does seem clear that glibc got confused about the union size.

This ticket is a bit old. Could someone please try turning on fortify source with a current 5.2.x version
and see if there is a problem. If there is I will fix it. That said, I still recommend against using fortify
source, as I previously wrote, Bacula has all its own routines since 10 years so adding fortify source
will only add unnecessary additional overhead.

Just the same, I would like to see this ticket closed one way or another.

The current bacula version (15.0.3-3) still undefines _FORTIFY_SOURCE in src/bacula.h

This bug was fixed in the package bacula - 15.0.3-3ubuntu1

---------------
bacula (15.0.3-3ubuntu1) questing; urgency=medium

  * d/p/enable-fortification: enable libc fortifications (LP: #265102)
  * d/control: move mt-st from recommended to suggested (LP 2112455)
  * d/bacula-director-db.postinst: use UTF8 encoding for new postgresql databases
  * d/scripts/install-dbconfig: fix shell quoting by sed instead of patch
    (LP: #1882032)

 -- Jonas Jelten <email address hidden> Tue, 24 Jun 2025 15:23:34 +0000