<feed xmlns='http://www.w3.org/2005/Atom'>
<title>fscrypt.git/cli-tests/t_not_enabled.sh, branch v0.3.3</title>
<subtitle>Go tool for managing Linux filesystem encryption
</subtitle>
<id>https://git.hodgden.net/cgit.cgi/fscrypt.git/atom?h=v0.3.3</id>
<link rel='self' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/atom?h=v0.3.3'/>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/'/>
<updated>2020-05-09T22:21:31Z</updated>
<entry>
<title>filesystem: improve errors</title>
<updated>2020-05-09T22:21:31Z</updated>
<author>
<name>Eric Biggers</name>
<email>ebiggers@google.com</email>
</author>
<published>2020-05-09T21:52:07Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=66fb4c557644ba2c37951a7568c06c47a6c718a7'/>
<id>urn:sha1:66fb4c557644ba2c37951a7568c06c47a6c718a7</id>
<content type='text'>
Introduce filesystem.ErrEncryptionNotEnabled and
filesystem.ErrEncryptionNotSupported which include the Mount as context,
and translate the corresponding metadata/ errors into them.  Then make
these errors show much better suggestions.

Also replace lots of other filesystem/ errors with either custom types
or with unnamed one-off errors that include more context.  Fix backwards
wrapping in lots of cases.

Finally, don't include the mountpoint in places where it's not useful,
like OS-level errors that already include the path.
</content>
</entry>
<entry>
<title>cli-tests: add t_not_enabled</title>
<updated>2020-05-09T21:04:47Z</updated>
<author>
<name>Eric Biggers</name>
<email>ebiggers@google.com</email>
</author>
<published>2020-05-09T21:04:47Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=c5faa27f1ff51d9fe7e6453a6e92b032c82b3c43'/>
<id>urn:sha1:c5faa27f1ff51d9fe7e6453a6e92b032c82b3c43</id>
<content type='text'>
Test that fscrypt fails when the filesystem doesn't have the encrypt
feature enabled.  Then test enabling it.
</content>
</entry>
</feed>
