Filesystem with Interactive Access Control for Linux
fedir
bfc22c79e0
Passthrough is usable now. There have been issues with the `access` operation: it's unclear what it must return, since the answer isn't known at the time when it is called. If it always returns "denied", many applications would finish without trying to open a file, thinking the access would not be granted after `access` call. Although always returning "permitted" seems like a better choice, it still might cause unexpected behaviour. Perhaps one way to solve this, is actually asking user whether to allow access. In any case, this issue needs to be looked into. |
||
|---|---|---|
| docs | ||
| sources | ||
| .gitignore | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
ICFS -- Interactively Controlled File System
Motivation
Traditional access control mechanisms in operating systems allow the same level of access to all processes running on behalf of the same user. This typically enables malicious processes to read and/or modify all data accessible to the user running a vulnerable application. It can be dealt using various mandatory access control mechanisms, but these are often complicated to configure and are rarely used in common user oriented scenarios. This thesis focuses on design and implementation of a file system layer which delegates the decision to allow or deny access to a file system object by a specific process to the user.
Goals
- Analyze the problem and design a solution
- Implement the solution using the FUSE framework
- Test the solution and demonstrate its benefits
Docs
Credit
Student: Fedir Kovalov
Supervisor: RNDr. Jaroslav Janáček, PhD.