Code signing checking

2023-01-06 Thread Aandi Inston via Cocoa-dev
Is there any API for doing the following activities related to code signing? - Check that the signature on the running codesigned executable is from the same company as the signature on a bundle? OR - Get the company from the codesigned running executable and - Get the company from a signature on a

NSAppKitVersionNumber wrong on latest Big Sur versions?!

2023-01-06 Thread Sean McBride via Cocoa-dev
Hi all, On at least 3 Macs in my office, running macOS 11.7 or 11.7.2, NSAppKitVersionNumber (at runtime) is 2202.7 (sic). This conflicts with NSApplication.h which has: static const NSAppKitVersion NSAppKitVersionNumber11_0 = 2022; static const NSAppKitVersion NSAppKitVersionNumber11_1 = 2022

Re: NSAppKitVersionNumber wrong on latest Big Sur versions?!

2023-01-06 Thread Rob Petrovec via Cocoa-dev
Yes, this is a bug that started in 11.7 that doesn’t appear to have been fixed yet in 11.7.2. Have you tried the arguably more robust and less error prone runtime checks of: Swift if #available(macOS 10.16, *) { // macOS 10.16 or later code path } else { // code for earlier than 10.1

Re: Code signing checking

2023-01-06 Thread James Walker via Cocoa-dev
On 1/6/23 12:28 PM, Aandi Inston via Cocoa-dev wrote: Is there any API for doing the following activities related to code signing? - Check that the signature on the running codesigned executable is from the same company as the signature on a bundle? OR - Get the company from the codesigned runnin

Re: NSAppKitVersionNumber wrong on latest Big Sur versions?!

2023-01-06 Thread Sean McBride via Cocoa-dev
On 6 Jan 2023, at 16:27, Rob Petrovec wrote: > Yes, this is a bug that started in 11.7 that doesn’t appear to have been > fixed yet in 11.7.2. Thanks for the confirmation. Sad that such a serious regression wasn't fixed in 11.7.1 nor 11.7.2. > Have you tried the arguably more robust and less