Kext Invalid ownership

Question

Created Aug ’21

Replies 5

Boosts 0

Views 1.9k

Participants 2

So basically the problem starts in system preferences -> security & privacy. There is no allow button at all. I received letter from Apple that app is successfully notarised. Digging into the problem I've found that problem is with kext. So after sudo kextutil /pathtokext I see such errors in terminal:

Filesystem error: Invalid ownership (503:20) should be (0:0) on /private/var/db/KernelExtensionManagement/Staging/com.name.filesystems.P88h7Z/name.kext/Contents
Filesystem error: Invalid ownership (503:20) should be (0:0) on /private/var/db/KernelExtensionManagement/Staging/com.name.filesystems.P88h7Z/name.kext/Contents/_CodeSignature
Filesystem error: Invalid ownership (503:20) should be (0:0) on /private/var/db/KernelExtensionManagement/Staging/com.name.filesystems.P88h7Z/name.kext/Contents/_CodeSignature/CodeResources
Filesystem error: Invalid ownership (503:20) should be (0:0) on /private/var/db/KernelExtensionManagement/Staging/com.name.filesystems.P88h7Z/name.kext/Contents/MacOS
Filesystem error: Invalid ownership (503:20) should be (0:0) on /private/var/db/KernelExtensionManagement/Staging/com.name.filesystems.P88h7Z/name.kext/Contents/MacOS/name

Filesystem error: Invalid ownership (503:20) should be (0:0) on /private/var/db/KernelExtensionManagement/Staging/com.name.filesystems.P88h7Z/name.kext/Contents/Info.plist" UserInfo={NSLocalizedDescription=Validating extension failed: Kext name v2080.20 in executable kext bundle bundle name at name.filesystems.P88h7Z/name.kext:

Boost

Answer 1

DTS Engineer OP

Apple

Aug ’21

So after sudo kextutil /pathtokext …

What is /pathtokext in this example?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

VitaliiKizlov OP

Aug ’21

`/Users/vitaliikizlov/Desktop/Projects/MacOS/Mac/NordFS/nordfs.fs/Contents/Resources/mount_nordfs.app/Contents/Extensions/11/nordfs.kext

0

Answer 3

VitaliiKizlov OP

Aug ’21

Also there is another problem that after code sign and success notarization through Xcode (I receive letter from Apple) framework still shows that it's not notarized.

spctl -a -vv /Users/vitaliikizlov/Desktop/Projects/MacOS/Mac/NordFS/nordfs.fs/Contents/Resources/mount_nordfs.app

/Users/vitaliikizlov/Desktop/Projects/MacOS/Mac/NordFS/nordfs.fs/Contents/Resources/mount_nordfs.app: rejected

source=Unnotarized Developer ID

0

Answer 4

VitaliiKizlov OP

Aug ’21

Also after some investigation I have this error:

codesign -vvvv -R="notarized" --check-notarization /Users/vitaliikizlov/Desktop/Projects/MacOS/Mac/NordFS/nordfs.fs/Contents/Resources/mount_nordfs.app

/Users/vitaliikizlov/Desktop/Projects/MacOS/Mac/NordFS/nordfs.fs/Contents/Resources/mount_nordfs.app: valid on disk

/Users/vitaliikizlov/Desktop/Projects/MacOS/Mac/NordFS/nordfs.fs/Contents/Resources/mount_nordfs.app: satisfies its Designated Requirement

test-requirement: code failed to satisfy specified code requirement(s)

0

Answer 5

VitaliiKizlov OP

Aug ’21

Sorry, I've fixed everything. Problem was in incorrect codesign 🙂

0