Hi,
I'm currently working on a kernel modification to extend the EXT3 file
system to include encryption based on file ownership.
This is an experimental graduate project for Penn State that may result in a
proposed patch.
Each user and group has an encryption key and files are encrypted with
the key based on permissions. The issues is what should I do about
"root" access, since root has free access to everything. There are two
goals -- transparency (everything works like it did without encryption but
slower)
and security (for root it conflicts with transparency).
I can maintain free access -- but the overall security is weakened
since an attacker will only need to gain the root encryption key to
authenticate.
I can disallow access to files for root based on the permissions --
which may cause applications to stop working properly, since they may
count on root's special privlages.
I can allow access to files that are encrypted and root does not have
permissions to as ciphertext and the files root does have access to as
plaintext.
Other ideas are welcome.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |