|
Bugzilla – Full Text Bug Listing |
| Summary: | Postfix can't open sasl_passwd.db because "Operation not permitted" | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Holger Macht <hmacht> |
| Component: | AppArmor | Assignee: | Seth R Arnold <seth.arnold> |
| Status: | RESOLVED FIXED | QA Contact: | Dominic W Reynolds <dreynolds> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | aj, kukuk |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Holger Macht
2006-01-30 13:40:16 UTC
Seth can you look at this profile issue? Andreas - this is listed as a blocker for 10.1 - this has not been fixed for beta3. Thorsten - this will also affect SLES10. Holger, thanks for the report. Our next checkin will include a rule for postfix's smtp that includes read access to this specific file. If SASL is still not supported, please either run: aa-genprof /usr/lib/postfix/smtp and try sending mail again, or use the yast "novell apparmor / create profile" utility to do much the same thing. This will allow postfix's smtp sending service to run in "complain mode", where all access are granted and recorded. The aa-genprof utility will help you update the profile; once it works without error (which should be only one or two iterations of the aa-genprof tool), please send us the /etc/apparmor.d/usr.lib.postfix.smtp file. Assuming this single rule doesn't resolve the problem, of course. :) Please let me know if it doesn't. Thanks. Seth is this checked in for beta4? Can we close or do you still need more information from holger? Dominic, it's up to you -- this is checked into beta4, but as none of us have ever set up a SASL environment before, testing it would be difficult. We could close this bug as this specific problem has been addressed, but other problems might be lurking behind the one failed access... Close the bug and I will reopen it if there are remaining issues in beta4. Thanks |