[<prev] [next>] [day] [month] [year] [list]
Message-ID:
<MN2PR12MB308734AB7A84D25A20E5880EAB879@MN2PR12MB3087.namprd12.prod.outlook.com>
Date: Mon, 11 Jul 2022 20:11:38 +0000
From: Mike Granby <mikeg@...eg.net>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: _chk Variants
I have been trying to run a GCC cross-compiler within Alpine, and hitting an issue with musl not providing the _chk variants of various APIs. For example, glibc provides __printf_chk which takes an additional argument and optionally performs various security checks before proceeding. I know the official way forward is to rebuild the compiler with the option to disable these calls, but rebuilding the GCC toolchain is not for the faint of heart, and I have thus been loath to go down that path. Instead, I developed a patch for the Alpine's musl APK that implemented the _chk variants as mere wrappers for the underlying APIs, thus allowing GCC to operate, albeit without the extra security that a full implementation would provide. This met my immediate need, but I am interested as to the view of the community in either implementing the _chk variants for real, or in providing the wrappers to enable better binary compatibility.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
