<feed xmlns='http://www.w3.org/2005/Atom'>
<title>fscrypt.git/cmd/fscrypt, branch v0.2.0</title>
<subtitle>Go tool for managing Linux filesystem encryption
</subtitle>
<id>https://git.hodgden.net/cgit.cgi/fscrypt.git/atom?h=v0.2.0</id>
<link rel='self' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/atom?h=v0.2.0'/>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/'/>
<updated>2017-08-22T19:53:26Z</updated>
<entry>
<title>security: Moved cache dropping function</title>
<updated>2017-08-22T19:53:26Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-08-22T19:52:41Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=32c9be59a2485ef44ac4b3accc2f102cf2eb5a39'/>
<id>urn:sha1:32c9be59a2485ef44ac4b3accc2f102cf2eb5a39</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cmd/fscrypt: purge command now clears cache</title>
<updated>2017-08-18T05:49:44Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-08-16T01:11:29Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=151e8965fa3a9c8f65e316430f9df0fa763fb02d'/>
<id>urn:sha1:151e8965fa3a9c8f65e316430f9df0fa763fb02d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cmd/fscrypt: fix help message for ErrKeyFileLength</title>
<updated>2017-08-07T16:56:19Z</updated>
<author>
<name>Eric Biggers</name>
<email>ebiggers@google.com</email>
</author>
<published>2017-08-07T16:51:20Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=ddc15e139fb8748ad06722944be1968c0d55803d'/>
<id>urn:sha1:ddc15e139fb8748ad06722944be1968c0d55803d</id>
<content type='text'>
The key file for the raw_key source is required to contain a wrapping
key (32 bytes), not a policy key (64 bytes).
</content>
</entry>
<entry>
<title>cmd/fscrypt: more nits to fix "make lint"</title>
<updated>2017-07-18T06:20:51Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-07-18T06:18:49Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=e4cb9c6cef2d75cdc5ca62777d2fa0e44f813fd4'/>
<id>urn:sha1:e4cb9c6cef2d75cdc5ca62777d2fa0e44f813fd4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cmd/fscrypt: username and login token fix</title>
<updated>2017-07-18T00:30:46Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-07-18T00:30:46Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=1a4a020ad5766fce3b3ad719d85593a3e8159733'/>
<id>urn:sha1:1a4a020ad5766fce3b3ad719d85593a3e8159733</id>
<content type='text'>
The commit changes how we get the username representation, and uses the
new pam API for checking the proposed login token.
</content>
</entry>
<entry>
<title>cmd/fscrypt: prompts now use command functions</title>
<updated>2017-07-17T22:08:19Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-07-17T22:08:19Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=f03dc9e84eea127f0efc3db21375abbafa78ce59'/>
<id>urn:sha1:f03dc9e84eea127f0efc3db21375abbafa78ce59</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cmd/fscrypt: Improve "fscrypt status"</title>
<updated>2017-07-17T20:21:11Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-07-17T20:21:11Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=5d727874440e4e451b45baba4ad7e277b9399730'/>
<id>urn:sha1:5d727874440e4e451b45baba4ad7e277b9399730</id>
<content type='text'>
Now that we can distinguish between lacking encryption support and
lacking fscrypt metadata, "fscrypt status" can now display this
additional information.
</content>
</entry>
<entry>
<title>cmd/fscrypt: Check support before encrypting</title>
<updated>2017-07-17T20:19:43Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-07-17T20:19:43Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=d0efe1f27b4229011292c076b923db985bcb6de4'/>
<id>urn:sha1:d0efe1f27b4229011292c076b923db985bcb6de4</id>
<content type='text'>
Almost all actions only need to to check that the fscrypt metadata
exists (this is handled by the Mount methods). Only "fscrypt encrypt"
need to be sure the filesystem also supports encryption, so this check
is added.
</content>
</entry>
<entry>
<title>cmd/fscrypt: fix protector and policy cleanup</title>
<updated>2017-07-14T18:32:41Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-07-14T18:32:41Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=9272c344cfcc7f4b153c408d05b57175bb1095cf'/>
<id>urn:sha1:9272c344cfcc7f4b153c408d05b57175bb1095cf</id>
<content type='text'>
Protectors are only reverted if they were created, and Policies are only
depovisioned on failure.
</content>
</entry>
<entry>
<title>Finalize import paths and documentation</title>
<updated>2017-06-28T22:15:21Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-06-28T20:57:55Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=2c52eca8727df744d093703bbcbd87fc39d57d30'/>
<id>urn:sha1:2c52eca8727df744d093703bbcbd87fc39d57d30</id>
<content type='text'>
This commit changes all the internal import paths from `fscrypt/foo` to
`github.com/google/fscrypt/foo` so that it can be built once we release
externaly. The documentation in README.md is updated accordingly.

Also, the README has a note noting that we do not make any guarantees
about project stability before 1.0 (when it ships with Ubuntu).

Change-Id: I6ba86e442c74057c8a06ba32a42e17f94833e280
</content>
</entry>
</feed>
