[Bug 295485] need a way to block zfs.ko from being autoloaded by tools like puppet and facter
[email protected] Sun, 24 May 2026 05:42:22 +0000
| Newsgroups | gmane.os.freebsd.devel.file-systems |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295485 --- Comment #13 from Mark Millard <[email protected]> --- (In reply to Dan Mahoney from comment #12) You can edit your subject line at will if you want to. (Most folks cannot edit it.) Thanks for the other notes. Going in a different direction, I do not know if I should believe this google-search AI report about puppet/openvox: QUOTE zfs_core can be omitted, provided your infrastructure does not rely on ZFS features. Puppet: The zfs_core module is only required if you actively manage ZFS datasets or Zpools via Puppet’s built-in zfs and zpool resource types. If your servers do not run ZFS, it can be safely removed from your Puppetfile or module directory. OpenVox: Because OpenVox is a drop-in, community-driven fork of the legacy open-source Puppet agent, it treats modules the exact same way. If you do not use ZFS, you do not need the ZFS provider. You can simply omit the puppetlabs-zfs_core or zfs_core module from your environment unless you use ZFS filesystems in your local environment. END QUOTE Is there any chance that such puppet/openvox configuration changes could deal with the issue where ZFS is not in use, at least until you get all the various supported OS's to have the kind of thing that you are asking FreeBSD for? Anyway, overall it is an interesting problem when a loadable kernel model can be a contribution to a CVE context. But I'll stop asking questions. -- You are receiving this mail because: You are the assignee for the bug.