Hello,

I think the patch (and $SUBJECT) speaks for itsself ;-)

=== modified file 'parser/parser_yacc.y'
--- parser/parser_yacc.y        2013-09-28 00:26:39 +0000
+++ parser/parser_yacc.y        2013-12-06 18:52:41 +0000
@@ -657,7 +657,7 @@
 rules:  rules opt_prefix mnt_rule
        {
                if ($2.owner)
-                       yyerror(_("owner prefix not allow on mount rules"));
+                       yyerror(_("owner prefix not allowed on mount rules"));
                if ($2.deny && $2.audit) {
                        $3->deny = 1;
                } else if ($2.deny) {
@@ -674,7 +674,7 @@
 rules:  rules opt_prefix dbus_rule
        {
                if ($2.owner)
-                       yyerror(_("owner prefix not allow on dbus rules"));
+                       yyerror(_("owner prefix not allowed on dbus rules"));
                if ($2.deny && $2.audit) {
                        $3->deny = 1;
                } else if ($2.deny) {
@@ -701,7 +701,7 @@
 rules:  rules opt_prefix capability
        {
                if ($2.owner)
-                       yyerror(_("owner prefix not allow on capability 
rules"));
+                       yyerror(_("owner prefix not allowed on capability 
rules"));
 
                if ($2.deny)
                        $1->caps.deny |= $3;



Regards,

Christian Boltz
-- 
> Am Besten wäre natürlich, den Owner von /dev/usbkabel ;-) zu
> überprüfen *g*
Dieses Device ist IMHO aber erst im neuen Kernel vorgesehen. Hast
Du da etwa schon einen Patch für den SuSE-Kernel? ;-)
[> Christian Boltz und Harald Krause in suse-linux]


-- 
AppArmor mailing list
AppArmor@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/apparmor

Reply via email to