[snap] Permission denied on Private encrypted folder
Bug #1848919 reported by
Alex N.
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
Fix Released
|
Low
|
Jamie Strandboge | ||
snapd |
Fix Released
|
Low
|
Jamie Strandboge | ||
apparmor (Ubuntu) |
Fix Released
|
Medium
|
Jamie Strandboge | ||
chromium-browser (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
snapd (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
When accessing the Private (/home/
Package: chromium-browser
Version: 77.0.3865.
description: | updated |
Changed in snapd (Ubuntu): | |
status: | Triaged → In Progress |
Changed in apparmor: | |
status: | New → Triaged |
importance: | Undecided → Low |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in apparmor: | |
status: | Triaged → In Progress |
Changed in apparmor: | |
status: | In Progress → Fix Released |
Changed in apparmor (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in snapd: | |
status: | In Progress → Fix Released |
Changed in snapd (Ubuntu): | |
status: | Triaged → Fix Released |
To post a comment you must log in.
I can reliably reproduce the issue after creating an encrypted Private directory with ecryptfs- setup-private (see https:/ /help.ubuntu. com/community/ EncryptedPrivat eDirectory# Setup_Your_ Encrypted_ Private_ Directory).
The problem stems from the fact that the home interface doesn't allow reading/writing to hidden folders in $HOME, and the ~/Private folder is actually backed by encrypted data in ~/.Private.
This is not specific to chromium, other strictly confined snaps using the home interface would be similarly affected.
Interestingly, saving a file to the folder still works, despite the error and the fact that the file dialog is unable to show the contents of the folder.