Skip to content

GitLab

Switch branch/tag
  1. 28 Jan, 2015 1 commit
  3. 23 Jan, 2015 2 commits
    • Kenny Root's avatar
      Merge "Remove superfluous OpenSSL include paths." · 26970299
      Kenny Root authored
      26970299
    • Adam Langley's avatar
      Remove superfluous OpenSSL include paths. · 41405bb3
      Adam Langley authored 
      The libcrypto and libssl modules (and their respective static and host
versions) use LOCAL_EXPORT_C_INCLUDE_DIRS thus just including the module
is sufficient.

Additionally, cryptfs.h was including an OpenSSL header just to get the
length of a SHA-256 hash. Rather than force all users of this header to
also depend on libcrypto, it's easier just to define that value in the
header file.

Change-Id: I3e3e0db906a212e1093944b298e4a8ff2e2fb07d
      41405bb3
  5. 06 Jan, 2015 2 commits
  7. 29 Dec, 2014 2 commits
  9. 18 Dec, 2014 4 commits
  11. 13 Dec, 2014 2 commits
    • Dan Albert's avatar
      Merge "Move vold to GCC." · a20bb17e
      Dan Albert authored
      a20bb17e
    • Dan Albert's avatar
      Move vold to GCC. · 084f0b3d
      Dan Albert authored 
      It looks like clang might have a miscompile that is causing SIGBUS in
`ioctl_init` when the device is encrypted. Move back to GCC until we
can sort this out.

Bug: 18736778
Change-Id: I21ae3b9d7d9ebff8679ecc1a828b7c59f27d0903
      084f0b3d
  13. 06 Nov, 2014 3 commits
  15. 05 Nov, 2014 1 commit
  17. 21 Oct, 2014 2 commits
  19. 18 Oct, 2014 2 commits
  21. 17 Oct, 2014 1 commit
  23. 16 Oct, 2014 2 commits
  25. 10 Oct, 2014 1 commit
  27. 06 Oct, 2014 2 commits
    • Paul Lawrence's avatar
      am fc615041: Remove possibility of zero chars from passwords · fd2180a9
      Paul Lawrence authored 
      * commit 'fc615041':
  Remove possibility of zero chars from passwords
      fd2180a9
    • Paul Lawrence's avatar
      Remove possibility of zero chars from passwords · fc615041
      Paul Lawrence authored 
      scrypt pads the password with zeros. Our patterns use 0 to represent
the top left dot. So patterns that end there are equivalent to ones
that end one short.

After much thought, the best solution is to change the way we
represent patterns in keyguard. This, however, is a big change.

The short term solution is to change the pattern representation in vold
so that we are storing the correct thing. Later we will change keyguard
to handle patterns correctly and remove quite a few hacks from vold
(use of hex, this code). b/17840293 created to track this.

Bug: 17751714
Change-Id: I30cdffb0f0db406d2e2b6c54d4153d120d975318
      fc615041
  29. 05 Oct, 2014 3 commits
  31. 03 Oct, 2014 2 commits
  33. 30 Sep, 2014 3 commits
    • Stephen Smalley's avatar
      Set SELinux contexts on device nodes created by vold. · 684e6625
      Stephen Smalley authored 
      
Extend vold to look up and set SELinux contexts on the
device nodes it creates for extra loop devices and for volumes.
Prior to this change, these device nodes simply inherited the type
of their parent directory /dev/block, i.e. block_device, and vold
therefore required create_file perms to block_device:blk_file.
With this change we can scope vold down to accessing specific
block device types.

This depends on change Id3bea28f5958086716cd3db055bea309b3b5fa5a
to allow vold to use setfscreatecon().

Change-Id: Ib9e8294abb1da94d92503947603ec12e802ff08c
Signed-off-by: default avatarStephen Smalley <sds@tycho.nsa.gov>
      684e6625
    • Paul Lawrence's avatar
      am 9c58a871: Use monotonic clock for cryptfs progress · f2eabef8
      Paul Lawrence authored 
      * commit '9c58a871':
  Use monotonic clock for cryptfs progress
      f2eabef8
    • Paul Lawrence's avatar
      Use monotonic clock for cryptfs progress · 9c58a871
      Paul Lawrence authored 
      Otherwise we get strange results when the time changes. Worst
effect is that the encryption takes a lot longer since we are
calling the logging code far more frequently.

Bug: 17625981
Change-Id: Ice29f28b3720e9e4a1ea28e45eeab574d1959ec1
      9c58a871
  35. 24 Sep, 2014 5 commits