<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-dev/fs/verity/Kconfig, branch master</title>
<subtitle>Linux kernel development work - see feature branches</subtitle>
<id>https://git.zx2c4.com/linux-dev/atom/fs/verity/Kconfig?h=master</id>
<link rel='self' href='https://git.zx2c4.com/linux-dev/atom/fs/verity/Kconfig?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/'/>
<updated>2022-07-16T06:42:30Z</updated>
<entry>
<title>fs-verity: mention btrfs support</title>
<updated>2022-07-16T06:42:30Z</updated>
<author>
<name>Eric Biggers</name>
<email>ebiggers@google.com</email>
</author>
<published>2022-06-10T00:06:16Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=8da572c52a9be6d006bae290339c629fc6501910'/>
<id>urn:sha1:8da572c52a9be6d006bae290339c629fc6501910</id>
<content type='text'>
btrfs supports fs-verity since Linux v5.15.  Document this.

Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;
Acked-by: David Sterba &lt;dsterba@suse.com&gt;
Link: https://lore.kernel.org/r/20220610000616.18225-1-ebiggers@kernel.org
</content>
</entry>
<entry>
<title>fs-verity: define a function to return the integrity protected file digest</title>
<updated>2022-05-01T20:39:36Z</updated>
<author>
<name>Mimi Zohar</name>
<email>zohar@linux.ibm.com</email>
</author>
<published>2021-11-23T18:37:52Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=246d921646c071b878480997c294db6c83215b06'/>
<id>urn:sha1:246d921646c071b878480997c294db6c83215b06</id>
<content type='text'>
Define a function named fsverity_get_digest() to return the verity file
digest and the associated hash algorithm (enum hash_algo).

This assumes that before calling fsverity_get_digest() the file must have
been opened, which is even true for the IMA measure/appraise on file
open policy rule use case (func=FILE_CHECK).  do_open() calls vfs_open()
immediately prior to ima_file_check().

Acked-by: Eric Biggers &lt;ebiggers@google.com&gt;
Signed-off-by: Mimi Zohar &lt;zohar@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>fsverity: relax build time dependency on CRYPTO_SHA256</title>
<updated>2021-04-22T07:31:32Z</updated>
<author>
<name>Ard Biesheuvel</name>
<email>ardb@kernel.org</email>
</author>
<published>2021-04-21T07:55:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=e3a606f2c544b231f6079c8c5fea451e772e1139'/>
<id>urn:sha1:e3a606f2c544b231f6079c8c5fea451e772e1139</id>
<content type='text'>
CONFIG_CRYPTO_SHA256 denotes the generic C implementation of the SHA-256
shash algorithm, which is selected as the default crypto shash provider
for fsverity. However, fsverity has no strict link time dependency, and
the same shash could be exposed by an optimized implementation, and arm64
has a number of those (scalar, NEON-based and one based on special crypto
instructions). In such cases, it makes little sense to require that the
generic C implementation is incorporated as well, given that it will never
be called.

To address this, relax the 'select' clause to 'imply' so that the generic
driver can be omitted from the build if desired.

Acked-by: Eric Biggers &lt;ebiggers@google.com&gt;
Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>fs-verity: support builtin file signatures</title>
<updated>2019-08-13T02:33:50Z</updated>
<author>
<name>Eric Biggers</name>
<email>ebiggers@google.com</email>
</author>
<published>2019-07-22T16:26:23Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=432434c9f8e18cb4cf0fe05bc3eeceada0e10dc6'/>
<id>urn:sha1:432434c9f8e18cb4cf0fe05bc3eeceada0e10dc6</id>
<content type='text'>
To meet some users' needs, add optional support for having fs-verity
handle a portion of the authentication policy in the kernel.  An
".fs-verity" keyring is created to which X.509 certificates can be
added; then a sysctl 'fs.verity.require_signatures' can be set to cause
the kernel to enforce that all fs-verity files contain a signature of
their file measurement by a key in this keyring.

See the "Built-in signature verification" section of
Documentation/filesystems/fsverity.rst for the full documentation.

Reviewed-by: Theodore Ts'o &lt;tytso@mit.edu&gt;
Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;
</content>
</entry>
<entry>
<title>fs-verity: add Kconfig and the helper functions for hashing</title>
<updated>2019-07-28T23:59:16Z</updated>
<author>
<name>Eric Biggers</name>
<email>ebiggers@google.com</email>
</author>
<published>2019-07-22T16:26:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=671e67b47e9fffd12c8f69eda853a202cb5b3fc5'/>
<id>urn:sha1:671e67b47e9fffd12c8f69eda853a202cb5b3fc5</id>
<content type='text'>
Add the beginnings of the fs/verity/ support layer, including the
Kconfig option and various helper functions for hashing.  To start, only
SHA-256 is supported, but other hash algorithms can easily be added.

Reviewed-by: Theodore Ts'o &lt;tytso@mit.edu&gt;
Reviewed-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;
</content>
</entry>
</feed>
