https://bugs.documentfoundation.org/show_bug.cgi?id=152579

--- Comment #3 from Sierk Bornemann <[email protected]> ---
Reading the release notes of Xcode 26 Beta 1 released yesterday, this info in
the section Security comes to my attention, which might be additionally very
helpful to know providing LibreOffice on macOS with pointer authentication
enabled and shipped as arm64e binary rather than arm64 binary:

Apple Developer: Xcode 26 Beta Release Notes – Section Security
https://developer.apple.com/documentation/xcode-release-notes/xcode-26-release-notes#Security

<quote>
…

Security
New Features

• […]

• Xcode now provides an “Enhanced Security” capability, which enables
additional runtime and compile-time protections for your application and builds
it with pointer authentication enabled. For more information see
https://developer.apple.com/documentation/xcode/enabling-enhanced-security-for-your-app
(143278278)

• […]

…
</quote>


while having special attention to section Prepare your app for pointer
authentication in the further document referred to therein:

Apple Developer: Enabling enhanced security for your app – Section Prepare your
app for pointer authentication
https://developer.apple.com/documentation/xcode/enabling-enhanced-security-for-your-app#Prepare-your-app-for-pointer-authentication

<quote>
…

Prepare your app for pointer authentication

The Enhanced Security capability includes additional runtime platform
restrictions, which Xcode enables by default for your app when you adopt the
capability by setting the ENABLE_POINTER_AUTHENTICATION build setting to Yes.
With these additional runtime platform restrictions enabled, Xcode builds your
app for the arm64e architecture and enables pointer authentication.

When pointer authentication is enabled, the system generates […]

…

If you need to turn off pointer authentication for your target, uncheck the
Authenticate Pointers checkbox in the Signing and Capabilities editor, or set
the ENABLE_POINTER_AUTHENTICATION build setting to No.

…
</quote>

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to