There have some kernel mechanisms that they keep symmetric key or password in memory. Those password or key may leak through /dev/mem, kdump, hibernation, bpf print to userland.

I want to think a design to:

  • Collect those sensitive data in a place

  • To avoid sensitive data are leaked through interface to userland.

  • Low overhead when getting data and checking sensitive memory area.

Looking for mad skills in:

Nothing? Add some keywords!

This project is part of:

Hack Week 15

Activity

  • almost 3 years ago: joeyli started kernel sensitive data protection
  • almost 3 years ago: joeyli originated kernel sensitive data protection
  • Show History

    Comments

    • joeyli
      almost 3 years ago by joeyli | Reply

      Upstream discussion about dm-crypt uses keyring: http://www.saout.de/pipermail/dm-crypt/2014-December/004525.html

    • joeyli
      almost 3 years ago by joeyli | Reply

      After c538f6ec in v4.10-rc1, the dm-crypt can use "user" or "logon" key type from keyring. But it doesn't support encrypted key type.

    • joeyli
      almost 3 years ago by joeyli | Reply

      Base on the kernel doucment security/keys-trusted-encrypted.txt, EVM and eCryptfs used encrypted key type.

    • joeyli
      almost 3 years ago by joeyli | Reply

      Looks the master keys in keyring that they are also the sensitive data. Need to check the detail of keyring.

    • joeyli
      almost 3 years ago by joeyli | Reply

      Crypto codes like AES expands key to the crypto context in tfm. So the crypto context also includes key as sensitive data.

    Similar Projects

    This project is one of its kind!