consider better handling for .pyc files
Bug #1496895 reported by
Jamie Strandboge
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Python snaps are trying to manipulate .pyc files in the system and read-only install directories and the security policy has (or will very soon) explicit deny rules:
deny /usr/lib/
deny /usr/lib/
deny @{CLICK_
this violates the snappy FHS. For now, this is ok-- the security policy is blocking the access without logging and the apps will run fine. However, the .pyc files are not being utilized so perhaps there is a way that the .pyc files could be written out in SNAP_APP_DATA_PATH somewhere instead of the readonly areas?
Related branches
| Changed in ubuntu-core-security (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Jamie Strandboge (jdstrand) |
| no longer affects: | ubuntu-core-security (Ubuntu) |
| Changed in snappy: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| affects: | snappy → snapd |
To post a comment you must log in.
