The official Chromium PPA is no longer maintained, so Alex somethingorother made an unofficial PPA that he keeps updated, and that's the PPA I'm using. However, for a while, he no longer updated his PPA, but just recently the first update in a while came out (Chromium 26.0.1386.0). I installed it, but it's requesting weird AppArmor permissions.
These are the lines I had to add to my AppArmor profile to allow Chromium to start (without this it exits with a segmentation fault):
The lines that concern me the most are in bold. Now why would a Chromium PPA which has been dormant for a little while, suddenly start requesting access to a bunch of package installation-related files, when it never needed to before? What's especially concerning is that it requires execution access to dpkg, and read access to every PPA list file in /etc/apt/sources.list.d/.
Could the unofficial PPA be compromised? Am I safe allowing it to access these things?