| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2017-10-19 | Random changesext4 | Joseph Richey | |
| 2017-10-19 | Move around and fscrypt refactor | Joe Richey joerichey@google.com | |
| 2017-10-02 | security: Sync filesystem before dropping caches | Joe Richey joerichey@google.com | |
| 2017-09-29 | Fix lint | Joseph Richey | |
| 2017-09-29 | security: Add check option to UserKeyringID | Joseph Richey | |
| 2017-09-01 | security: Change user keyring lookup algorithm | Joseph Richey | |
| Now instead of spawning a seperate thread we alternate between changing the euid and ruid to both find the keyring and link it to the process keyring. Note that we also ensure that the user keyring is linked into the root keyring whenever possible. | |||
| 2017-09-01 | security: No more permenant privilege dropping | Joseph Richey | |
| This was creating an issue becasuse fully dropping privileges required spawning a goroutine and using rutime.DropOSThread(). | |||
| 2017-08-31 | security: Error if privilege reset goes wrong | Joe Richey | |
| 2017-08-31 | Fixed linter issues | Joe Richey | |
| 2017-08-30 | security: Rewrite of keryings and permissions | Joe Richey | |
| The keyring lookup functions no longer read from /proc/keys. Now they simply spawn a thread, drop privs, and check with GetKeyringID and KEY_SPEC_USER_KEYRING. See userKeyringID() for more info. The privileges functions have also been changed. Now the concept of setting privileges is seperate form the concept of setting up the keyrings. | |||
| 2017-08-23 | security: fscrypt now possesses the user keyring | Joseph Richey | |
| 2017-08-23 | Added some documentation and improved security API | Joe Richey joerichey@google.com | |
| 2017-08-22 | security: Moved cache dropping function | Joe Richey joerichey@google.com | |
| 2017-08-22 | security: Fixed typo and improved error handling | Joe Richey joerichey@google.com | |
| 2017-08-17 | cmd/fscrypt: purge command now clears cache | Joe Richey joerichey@google.com | |