I echo ahasenack's question. /etc/letsencrypt/** is pretty broad (especially if it contains private keys).
Once those details are worked out, updating slapd is conceptually fine. We may want to consider updating the ssl_certs and ssl_keys abstractions accordingly if letsencrypt organizing things clearly. (We could also create a letsencrypt abstraction, but let's not go there just yet). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1805178 Title: Apparmor should include letsencrypt directory for Slapd Status in openldap package in Ubuntu: Incomplete Bug description: Apparmor denies access to /etc/letsencrypt for slapd, which is confusing for users trying to secure ldap with Letsencrypt in a stock configuration. The fix is inserting the following line in /etc/apparmor.d/usr.sbin.slapd: /etc/letsencrypt/** r, and then refreshing the profile: # apparmor_parser -vr usr.sbin.slapd This line should simply be included. tarek : ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1805178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
