|
Bugzilla – Full Text Bug Listing |
| Summary: | Opera "could not read directory" error when ApArmor is enabled | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Dzmitry Prakapenka <4maillists> |
| Component: | AppArmor | Assignee: | Dominic W Reynolds <dreynolds> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Dzmitry Prakapenka
2005-11-20 06:04:25 UTC
Dzmitry, thank you for your report; if you would like to allow this access in your opera profile, please run "genprof opera" (and use opera as you normally do), or use the YaST interface to generate a profile for opera. (You can see a walkthrough of using genprof here: http://danieldk.org/apparmor//profile-example.html ) I'll make sure this access gets added to our profile set. Thanks. Closing. This has been addressed by inclusion of user-download abstractions in openSUSE10.2 for the opera profile in extras. For users wanting write access to other directories either logprof (to adjust the opera profile) or hand modification to /etc/apparmor.d/abstractions/user-download will configure the policy. |