https://bugzilla.novell.com/show_bug.cgi?id=270225 Summary: AppArmor-Yast: "Manually Add Profile" does not do what advertised Product: openSUSE 10.3 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: dreynolds@novell.com ReportedBy: al4321@gmail.com QAContact: dreynolds@novell.com It does very unexpected thing. This was very confusing when a user tried to add my profile by using Yast's "Manually add profile" module. Currently "Manually Add Profile" creates profiles instead of adding existing ones to the /etc/apparmor.d It should add a ready profile whenever it's located in /home/* or any other directory to /etc/apparmor.d, and instead it creates a new profile for the file/binary you specify. That is: take them from *any* location and add them to the working set. Currently this means copying an already existing profile to /etc/apparmor.d from any location. recommended solution: the current module should be renamed to "Manually Create Profile", and a new Yast module must be developed to really add profiles. The other module: "Add Profile Wizard" should also be renamed to "Create Profile Wizard" for consistency. BASICALLY: this bug report unifies a bug (problematic Yast-module name) and a feature request to develop new very simple Yast-Module. The new module's job is just copying files. No more and no less. It is important if someone (third-party) gives you an AppArmored profile and wants the customer to add it. The new module only has effect on the user, when third-party distributes AppArmored module separately from the main package. If the profile included in RPM, the new module doesn't add any value. Should I open separate feature-request to develop the new module ? -Alexey Eremenko "Technologov" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.