Our FUSE-based FS that works just fine in 10.11 won’t load in Sierra B5 & B6. 
I’m sure it loaded in earlier betas but I can’t swear to it because I didn’t 
keep earlier versions (and it’s hard to revert). Be that as it may, in 10.11 if 
I do

kextutil -tn /Library/Filesystems/our_fs.fs/Support/our_fs.kext

I get

Defaulting to kernel file '/System/Library/Kernels/kernel'
/Library/Filesystems/our_fs.fs/Support/our_fs.kext appears to be loadable 
(including linkage for on-disk libraries).

but in Sierra B6 (& B5), I get

Diagnostics for /Library/Filesystems/our_fs.fs/Support/our_fs.kext:
Code Signing Failure: code signature is invalid
/Library/Filesystems/our_fs.fs/Support/our_fs.kext appears to be loadable 
(including linkage for on-disk libraries).

running "codesign -d —deep -vvvv"

shows the same result in both:

Executable=/Library/Filesystems/our_fs.fs/Support/our_fs.kextContents/MacOS/our_fs
Identifier=com.blah.blah...
Format=bundle with Mach-O universal (i386 x86_64)
CodeDirectory v=20200 size=901 flags=0x0(none) hashes=37+3 location=embedded
Hash type=sha1 size=20
CandidateCDHash sha1=f3a6880aaca37eb799a83ee3b183a577da1453f1
Hash choices=sha1
Page size=4096
CDHash=f3a6880aaca37eb799a83ee3b183a577da1453f1
Signature size=8580
Authority=Developer ID Application: my client’s ID
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=5 Oct 2015, 14:34:59
Info.plist entries=18
TeamIdentifier=my client’s team ID
Sealed Resources version=2 rules=12 files=0
Internal requirements count=1 size=200

Except that on 10.11, it doesn’t report “Page size=4096” (is that significant?)

Anyone else seeing this? Have code-signing requirements changed for Sierra?

Many thanks for any help.


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list      (Filesystem-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/filesystem-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to