[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: package security auditing and isolation
From: |
Yuri Khan |
Subject: |
Re: package security auditing and isolation |
Date: |
Thu, 6 Apr 2017 21:57:38 +0700 |
On Thu, Apr 6, 2017 at 9:15 PM, Ted Zlatanov <address@hidden> wrote:
> 2) establishing isolation levels in the C core. Simply put, not all
> packages need to be able to run shell commands, delete or modify files,
> and so on. When the user installs or updates a package, if the needed
> access levels change, that should be noted and acknowledged.
“This package is requesting the following permissions:
* Monitor all your keystrokes
* Modify buffer contents
* Access the kill ring
* Read and write files”
- package security auditing and isolation, Ted Zlatanov, 2017/04/06
- Re: package security auditing and isolation, Stefan Monnier, 2017/04/06
- Re: package security auditing and isolation,
Yuri Khan <=
- Re: package security auditing and isolation, Ted Zlatanov, 2017/04/06
- Re: package security auditing and isolation, Stefan Monnier, 2017/04/06
- Re: package security auditing and isolation, Ted Zlatanov, 2017/04/06
- Re: package security auditing and isolation, Stefan Monnier, 2017/04/06
- Re: package security auditing and isolation, Ted Zlatanov, 2017/04/06
- Re: package security auditing and isolation, Tim Cross, 2017/04/07
- Re: package security auditing and isolation, Clément Pit-Claudel, 2017/04/06