codesign for booting

Question

I went to update the ZFS-on-boot instructions https://openzfsonosx.org/wiki/ZFS_on_Boot and attempted to boot Catalina, but we do have an issue with mounting root:

Loaded module v1.9.2-4-d4889d276e, ZFS pool version 5000, ZFS filesystem version 5
zfs_boot_publish_bootfs: publishing bootfs [rpool/ROOT/Catalina]
zfs_boot_publish_bootfs done
Got boot device = IOService:/IOResources/net_lundman_zfs_zvol/rpool/ZFSDatasetProxy/IOBlockStorageDriver/rpool Media/ZFSDatasetScheme/Catalina
BSD root: disk6s1, major 1, minor 23
hfs_ValidateHFSPlusVolumeHeader: unknown Volume Signature : 0
hfs_mount: hfs_mountfs returned error=22 for device unknown-dev
ZFS: zfs_vfs_mountroot
Setting readonly
Not booted from APFS, skipping apfs.util
boot _checkBrokenSignatureWithTeamIDFatal(LazyPath *, struct cs_blob *): no registered daemon port for check_broken_signature_with_teamid_fatal
mac_vnode_check_signature: /Library/Filesystems/zfs.fs/Contents/Resouces/mount_zfs: code signature validation failed fatally: 
 When validating /Library/Filesystems/zfs.fs/Contents/Resources/mount_zfs:
  The code contains a Team ID, but validating its signature failed.
Please check you system log.proc 5: load code signature error 4 for file "mount_zfs"
port is not ready for callouts
mount: /: Killed

该提问来源于开源项目：openzfsonosx/zfs

Answer 1

If mount_zfs is not codesigned, it has the same complaints about the libraries. So an unsigned, static, zfs binary named zfs_mount is the way to go.

It does seem to stall a bit later due to memory concerns though.