<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test/sys/dev/veriexec, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test/atom?h=main</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/'/>
<updated>2020-01-03T22:29:58Z</updated>
<entry>
<title>vfs: drop the mostly unused flags argument from VOP_UNLOCK</title>
<updated>2020-01-03T22:29:58Z</updated>
<author>
<name>Mateusz Guzik</name>
<email>mjg@FreeBSD.org</email>
</author>
<published>2020-01-03T22:29:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=b249ce48ea5560afdcff57e72a9880b7d3132434'/>
<id>urn:sha1:b249ce48ea5560afdcff57e72a9880b7d3132434</id>
<content type='text'>
Filesystems which want to use it in limited capacity can employ the
VOP_UNLOCK_FLAGS macro.

Reviewed by:	kib (previous version)
Differential Revision:	https://reviews.freebsd.org/D21427
</content>
</entry>
<entry>
<title>Add a new ioctl for the larger params struct that includes the label.</title>
<updated>2019-05-17T19:27:07Z</updated>
<author>
<name>Stephen J. Kiernan</name>
<email>stevek@FreeBSD.org</email>
</author>
<published>2019-05-17T19:27:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=942886743b18da416fd96e85787a49a8e160e060'/>
<id>urn:sha1:942886743b18da416fd96e85787a49a8e160e060</id>
<content type='text'>
We need to make the find_veriexec_file() function available publicly, so
rename it to mac_veriexec_metadata_find_file_info() and make it non-static.

Bump the version of the veriexec device interface so user space will know
the labelized version of fingerprint loading is available.

Approved by:	sjg
Obtained from:	Juniper Networks, Inc.
Differential Revision:	https://reviews.freebsd.org/D20295
</content>
</entry>
<entry>
<title>Add command to get version of the ioctl interface for the veriexec device.</title>
<updated>2019-05-17T18:25:53Z</updated>
<author>
<name>Stephen J. Kiernan</name>
<email>stevek@FreeBSD.org</email>
</author>
<published>2019-05-17T18:25:53Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=910013c6a8c398d4335c713c4a1416658f026afc'/>
<id>urn:sha1:910013c6a8c398d4335c713c4a1416658f026afc</id>
<content type='text'>
Obtained from:	Juniper Networks, Inc.
MFC after:	1 week
</content>
</entry>
<entry>
<title>Protect commands that are considered dangerous with checks for kmem write</title>
<updated>2019-05-17T18:02:26Z</updated>
<author>
<name>Stephen J. Kiernan</name>
<email>stevek@FreeBSD.org</email>
</author>
<published>2019-05-17T18:02:26Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=9ce904dfde0ce588eea3f090adf79f54a56c6c2e'/>
<id>urn:sha1:9ce904dfde0ce588eea3f090adf79f54a56c6c2e</id>
<content type='text'>
priv. This allows for MAC/veriexec to prevent apps that are not "trusted"
from using these commands.

Obtained from:	Juniper Networks, Inc.
MFC after:	1 week
</content>
</entry>
<entry>
<title>Device for user space to interface with MAC/veriexec.</title>
<updated>2018-06-20T00:48:46Z</updated>
<author>
<name>Stephen J. Kiernan</name>
<email>stevek@FreeBSD.org</email>
</author>
<published>2018-06-20T00:48:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=ed7b25da7828ebf46eb180ed5fd94f8ce42cc90d'/>
<id>urn:sha1:ed7b25da7828ebf46eb180ed5fd94f8ce42cc90d</id>
<content type='text'>
The veriexec device features the following ioctl commands:

VERIEXEC_ACTIVE
  Activate veriexec functionality
VERIEXEC_DEBUG_ON
  Enable debugging mode and increment or set the debug level
VERIEXEC_DEBUG_OFF
  Disable debugging mode
VERIEXEC_ENFORCE
  Enforce veriexec fingerprinting (and acitvate if not already)
VERIEXEC_GETSTATE
  Get current veriexec state
VERIEXEC_LOCK
  Lock changes to veriexec meta-data store
VERIEXEC_LOAD
  Load veriexec fingerprint if secure level is not raised (and passes the
  checks for VERIEXEC_SIGNED_LOAD)
VERIEXEC_SIGNED_LOAD
  Load veriexec fingerprints from loader that supports signed manifest
  (and thus we can be more lenient about secure level being raised.)
  Fingerprints can be loaded if the meta-data store is not locked. Also
  securelevel must not have been raised or some fingerprints must have
  already been loaded, otherwise it would be dangerous to allow loading.
  (Note: this assumes that the fingerprints in the meta-data store at
         least cover the fingerprint loader.)

Reviewed by:	jtl
Obtained from:	Juniper Networks, Inc.
Differential Revision:	https://reviews.freebsd.org/D8561
</content>
</entry>
</feed>
