[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1107956: marked as done (release-notes: Document CET hardening for amd64 (as companion to PAC/BTI on arm64))

Your message dated Fri, 18 Jul 2025 15:51:28 +0200
with message-id <aHpRYEkOvZ1Ncdq4@per.namespace.at>
and subject line Re: Bug#1107956: release-notes: Document CET hardening for amd64 (as companion to PAC/BTI on arm64)
has caused the Debian Bug report #1107956,
regarding release-notes: Document CET hardening for amd64 (as companion to PAC/BTI on arm64)
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 owner@bugs.debian.org
immediately.)


-- 
1107956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107956
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
X-Debbugs-Cc: Emanuele Rocca <ema@debian.org>

Hi!

There was a recent addition about PAC/BTI support for arm64. I think
it would make sense to also mention the Control-flow Enforcement
Technology (CET) support for amd64, that got added at the same time,
for the same dpkg-buildflags "branch" feature, which is also enabled
by default and ends up adding the «-fcf-protection» flag.

I'm not sure whether it would be best to reword the existing
"2.2.2. PAC/BTI support on arm64" section to cover both, or to add a
new section. Let me know what you think, and I could try to propose a
patch perhaps.

Thanks,
Guillem

--- End Message ---
--- Begin Message --- 
On Sun, Jun 22, 2025 at 01:11:25AM +0200, Chris Hofstaedtler wrote:
> Please somebody provide a patch, better: merge request.

Thank you Emanuele and Guillem for providing the merge request and 
iterating on it.

It was merged, thus closing this bug.

Best,
Chris

--- End Message ---
Reply to: