Bug #9895
Reproduce lack of permission error in FF38 when AppArmor denies access to a file
100%
Description
Since Tor Browser 5.0, based on Firefox ESR38, we do not get any “Permission denied” warning page when trying to open files that AppArmor will deny. If it can be reproduced in a vanilla FF38, then that’s a UX regression. If not, I suppose it’s a regression in introduced by the Tor Browser some how.
Subtasks
History
#1 Updated by anonym 2015-09-16 12:42:47
Interestingly, on my Debian Jessie system, with Tor Browser 5.0.2, I tried to browse some directory that was blocked, and I got a “Permission denied” or something page. However, now when I retry it, I get the same behavior as in Tails.
#2 Updated by anonym 2015-09-22 15:03:12
- Target version changed from Tails_1.6 to Tails_1.7
#3 Updated by anonym 2015-11-23 04:38:56
- Target version changed from Tails_1.7 to Tails_1.8
#4 Updated by intrigeri 2015-12-05 14:08:31
- Target version changed from Tails_1.8 to Tails_2.2
Postponing to after January, since times will be a bit crazy until then.
#5 Updated by anonym 2016-02-11 22:51:06
- % Done changed from 0 to 70
So I’ve done this now. I threw together an AppArmor profile denying only a specific folder + contents (where I then tried to access a file) and tested against iceweasel 38.6.0esr-1~deb8u1 on a Debian Jessie system. I get the same results as in Tails, i.e. no feedback whatsoever when permissions for a local file is denied by AppArmor.
However, I then checked a file that AppArmor allows, but which Unix file permissions deny reading, and then there’s no feedback either. I then disabled AppArmor, and tried the same file, and there’s no feedback then either. I then tested with Mozilla’s own Firefox linux builds, 38.6.1esr and 44.0.2, and it’s all the same. I even tried on a Windows system with Firefox 44.0.2 that I have access to, and it’s the same there!
So this is clearly a UX regression (IMHO) in upstream Firefox. But it’s all very odd, because I’ve seen a “Permission denied” page in the Tor Browser I use on my system when trying to reproduce this, although it only happened very rarely (most of the time I just got nothing).
#6 Updated by anonym 2016-02-11 23:31:23
- Status changed from Confirmed to Resolved
- Assignee deleted (
anonym) - % Done changed from 70 to 100
Reported upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1247779
Closing this ticket in favour of Bug #11106.