| 1 |
Recently I was watching some videos that was looking at vulnerabilities |
| 2 |
in IP camera systems and many of the fails that the security person was |
| 3 |
able to exploit were forgetting to lock down access to some directory or |
| 4 |
file so that he was able to first examine a program or script, and then |
| 5 |
determine points of access. With the discussion here I was wondering if |
| 6 |
there was any mechanism to turn all access off, and then 'grant' access |
| 7 |
to something. This may be similar to how Gentoo's USE flags can be |
| 8 |
likewise cleaned by: "USE = "-* X alsa..." |
| 9 |
|
| 10 |
Anyway, I browsed your tests and did not find anything and thought I |
| 11 |
might mention it. |
| 12 |
|
| 13 |
EBo -- |
| 14 |
|
| 15 |
On Jul 26 2020 5:00 PM, Kaoru Esashika wrote: |
| 16 |
> Hi, |
| 17 |
> This week, I wrote the code about ACL (Access Control List). |
| 18 |
> The ACL allows you to actually control whether or not the application |
| 19 |
> can access your files. |
| 20 |
> This implementation also includes an interface that allows you to |
| 21 |
> control access to the files dynamically. |
| 22 |
> Specifically, you can control access to specific files by writing a |
| 23 |
> list of files to be controlled in a special virtual file called a |
| 24 |
> control file. |
| 25 |
> |
| 26 |
> Next week, I will integrate the Fusebox with emerge/portage. And |
| 27 |
> also, |
| 28 |
> I need prepare to evaluation... |
| 29 |
> |
| 30 |
> Project Repository: https://github.com/pluser/fusebox |
| 31 |
> |
| 32 |
> Regards, |
| 33 |
> Kaoru Esashika |
Archives