From: Christian Melki <christian.melki@t2data.com>
To: ruggero rossi <rugrossi@googlemail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] PTXDIST 2025.09.0: build failure of openssl-3.5.2 when gcc option -fzero-call-used-regs is not supported
Date: Wed, 17 Sep 2025 11:18:31 +0200 [thread overview]
Message-ID: <ea633f3d-68a4-42f0-ab3c-12a035edf6e6@t2data.com> (raw)
In-Reply-To: <20250917110003.6587c431@RR-Laptop>
On 9/17/25 11:00 AM, ruggero rossi wrote:
> On Wed, 17 Sep 2025 10:30:04 +0200
> Christian Melki <christian.melki@t2data.com> wrote:
>
>> Hi.
>>
>> Which version of gcc are we talking about?
> It is quite old, but I'm bound to it because some software does not
> compile with newer versions. It looks like that the -fzero-call-used-regs
> is supported from GCC 11 (released April 2021).
>
>> GCC 11 should support this, but I don't know over which archs.
>> It is there as a security enhancement. I would say something like less
>> gadgets for ROP style attacks? And while it does slow down execution,
>> for something like OpenSSL, it usually is worth it imho.
> I agree.... The option is a must, when it is supported.
>
> Moreover, I found a comment in some openssh (not openssl) tracking,
> saying that to detect whether a version of gcc supports the option or not
> may be not trivial.
>
>> I don't see a suitable toolchain option or hardening flag in ptxdist
>> that currently fits this cleanly. Not sure if something like this fits
>> for a its own global pass either. Maybe someone else has another opinion.
>>
>> So my immediate suggestion would be to keep this local at your end for
>> now.
>
> OK - and these messages remain as a help if anyone else has the same
> problem.
Indeed. Appreciate the time taken to report it.
Christian
>
> Regards,
> Ruggero
>
>>
>> Regards,
>> Christian
prev parent reply other threads:[~2025-09-17 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 6:32 ruggero rossi via ptxdist
2025-09-17 8:30 ` Christian Melki
2025-09-17 9:00 ` ruggero rossi via ptxdist
2025-09-17 9:18 ` Christian Melki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea633f3d-68a4-42f0-ab3c-12a035edf6e6@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
--cc=rugrossi@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox