I'm still getting "modify_principal: Insufficient access to lock database" error messages when trying to use kadmin in enforcing mode.I ran 'semodule -DB' to re-enable don't audit messages, and I've attached what I get when trying to run a kadmin command to add a principal (after starting kadmind/krb5kdc... kadmin.log seems to be ok). Any hint, tips or policy modules greatly appreciated... -- Robert Story SPARTA
Attachment:
avcs
Description: Binary data
Attachment:
signature.asc
Description: PGP signature
-- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-selinux-list
