<feed xmlns='http://www.w3.org/2005/Atom'>
<title>fscrypt.git/cmd/fscrypt, branch v0.2.3</title>
<subtitle>Go tool for managing Linux filesystem encryption
</subtitle>
<id>https://git.hodgden.net/cgit.cgi/fscrypt.git/atom?h=v0.2.3</id>
<link rel='self' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/atom?h=v0.2.3'/>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/'/>
<updated>2018-02-12T07:56:49Z</updated>
<entry>
<title>vet: eliminate unnecessary shadowing</title>
<updated>2018-02-12T07:56:49Z</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey94@gmail.com</email>
</author>
<published>2018-02-12T07:56:49Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=69630f37fcebe894b15872148bd8b2496806b60c'/>
<id>urn:sha1:69630f37fcebe894b15872148bd8b2496806b60c</id>
<content type='text'>
Running "go vet -shadow ./..." finds all places where a variable might
be incorrectly or unnecessarily shadowed. This fixes some of them.
</content>
</entry>
<entry>
<title>cmd/fscrypt: don't show build time if not set</title>
<updated>2018-02-12T07:38:19Z</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey94@gmail.com</email>
</author>
<published>2018-02-12T07:38:19Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=1f508cc30f3c1caadea5c648158880eacfe9b113'/>
<id>urn:sha1:1f508cc30f3c1caadea5c648158880eacfe9b113</id>
<content type='text'>
</content>
</entry>
<entry>
<title>lint: Remove all build tags</title>
<updated>2018-02-12T04:13:01Z</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey94@gmail.com</email>
</author>
<published>2018-02-12T04:13:01Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=924b8d09db66868af7a6cf174d5346ace13dfa8a'/>
<id>urn:sha1:924b8d09db66868af7a6cf174d5346ace13dfa8a</id>
<content type='text'>
Our current build tags set off the linter. We will later add in more
comprehensive build tags that will be properly formatted.
</content>
</entry>
<entry>
<title>security: Sync filesystem before dropping caches</title>
<updated>2017-10-02T23:49:16Z</updated>
<author>
<name>Joe Richey joerichey@google.com</name>
<email>joerichey@google.com</email>
</author>
<published>2017-10-02T23:49:16Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=c6568945adb69a3b7779c0f9e0e1f427d31209ab'/>
<id>urn:sha1:c6568945adb69a3b7779c0f9e0e1f427d31209ab</id>
<content type='text'>
</content>
</entry>
<entry>
<title>security: Add check option to UserKeyringID</title>
<updated>2017-09-29T09:52:56Z</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey94@gmail.com</email>
</author>
<published>2017-09-29T09:52:56Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=4d9372795e7b53d105f69790c1d9deadbff85458'/>
<id>urn:sha1:4d9372795e7b53d105f69790c1d9deadbff85458</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fixes logging string for policies</title>
<updated>2017-09-07T01:16:03Z</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey@google.com</email>
</author>
<published>2017-09-07T01:16:03Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=a949b13dac670014c37c7181e368b9c0c7a7f0f5'/>
<id>urn:sha1:a949b13dac670014c37c7181e368b9c0c7a7f0f5</id>
<content type='text'>
We should always log the descriptor not the entire policy structure.</content>
</entry>
<entry>
<title>cmd/fscrypt: Add explanations for keyring failures</title>
<updated>2017-09-01T07:56:44Z</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey94@gmail.com</email>
</author>
<published>2017-09-01T07:56:44Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=0dfbbf62fae3d4051dd5f0686835ac393f8a0247'/>
<id>urn:sha1:0dfbbf62fae3d4051dd5f0686835ac393f8a0247</id>
<content type='text'>
Now the user is persented with help when they try to access a keyring
that isn't theirs or try to use fscrypt without a user keyring linked
into the session keyring.
</content>
</entry>
<entry>
<title>cmd/fscrypt: Check that keyrings are setup</title>
<updated>2017-09-01T07:55:22Z</updated>
<author>
<name>Joseph Richey</name>
<email>joerichey94@gmail.com</email>
</author>
<published>2017-09-01T07:55:22Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=079ee257d27e28b166965f1fa0136f694598b6c7'/>
<id>urn:sha1:079ee257d27e28b166965f1fa0136f694598b6c7</id>
<content type='text'>
Chaning the --user flag to (optionally) check for a proper keyring setup
allows us to fail early in cases where we need a working keyring.
</content>
</entry>
<entry>
<title>Fixed linter issues</title>
<updated>2017-08-31T18:29:30Z</updated>
<author>
<name>Joe Richey</name>
<email>joerichey@google.com</email>
</author>
<published>2017-08-31T18:29:30Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=5586bc35fbb33f20c38f52285c19c015b804ea94'/>
<id>urn:sha1:5586bc35fbb33f20c38f52285c19c015b804ea94</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cmd/fscrypt: Add --user flag for running as root</title>
<updated>2017-08-31T01:16:16Z</updated>
<author>
<name>Joe Richey</name>
<email>joerichey@google.com</email>
</author>
<published>2017-08-31T01:16:16Z</published>
<link rel='alternate' type='text/html' href='https://git.hodgden.net/cgit.cgi/fscrypt.git/commit/?id=11b31826334bc3faa4d4c7ee05a3b2996a88c969'/>
<id>urn:sha1:11b31826334bc3faa4d4c7ee05a3b2996a88c969</id>
<content type='text'>
The --user flag can now be used to have the targe user (the one whose
keyring and password will be used in fscrypt) be different than the
calling user. Very usefull for things like

	sudo fscrypt purge /media/joerichey/usb --user=joerichey

which will now have privileges to drop caches, but will properly clear
the keys from the user's keyring.
</content>
</entry>
</feed>
