We're in the process of trying to land these changes for thumbnailer, and have been noticing problems with the music-app: we are getting denials from aa_query_label for files under ~/Music. For example:
Is there something special about the way ~/Music access is enabled in the policy? I've been trying this out with devel-proposed (wily) image 233 on a Nexus 4 if that matters.
We're in the process of trying to land these changes for thumbnailer, and have been noticing problems with the music-app: we are getting denials from aa_query_label for files under ~/Music. For example:
$ ./query_file com.ubuntu. music_music_ 2.1.867 /home/phablet/ Music/10- amarillo. mp3 phablet/ Music/10- amarillo. mp3' denied
read '/home/
However, the profile seems to be able to read files in that location anyway:
$ aa-exec -p com.ubuntu. music_music_ 2.1.867 cat /home/phablet/ Music/10- amarillo. mp3 >/dev/null
It seems the aa_query_label checks are working for ~/.local/ share/$ PACKAGE directories though, so it is working at some level:
$ ./query_file com.ubuntu. music_music_ 2.1.867 /home/phablet/ .local/ share/com. ubuntu. music/foo phablet/ .local/ share/com. ubuntu. music/foo' allowed music_music_ 2.1.867 /home/phablet/ .local/ share/com. ubuntu. gallery/ foo phablet/ .local/ share/com. ubuntu. gallery/ foo' denied
read '/home/
$ ./query_file com.ubuntu.
read '/home/
Is there something special about the way ~/Music access is enabled in the policy? I've been trying this out with devel-proposed (wily) image 233 on a Nexus 4 if that matters.