apparmor_parser with --write-cache and --purge-cache should not delete CACHEDIR.TAG

Bug #1742427 reported by intrigeri
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AppArmor
New
Undecided
Unassigned
apparmor (Debian)
New
Undecided
Unassigned

Bug Description

Changed in apparmor (Debian):
status: Unknown → Confirmed
Revision history for this message
intrigeri (intrigeri) wrote :

The original problem this bug was about is gone. Actually, now that the multicache went in, we would instead install CACHEDIR.TAG in the cache-loc (/etc/apparmor.d/cache.d/CACHEDIR.TAG). It will apply recursively to all the actual cache sub-directories.

But the same practical problem comes back if using "apparmor_parser --purge-cache", which I would like to do on Debian scripts instead of having to maintain a shell implementation that does the same module it leaves CACHEDIR.TAG alone.

# touch /etc/apparmor.d/cache.d/CACHEDIR.TAG
# apparmor_parser --purge-cache
# ls /etc/apparmor.d/cache.d/CACHEDIR.TAG
ls: cannot access '/etc/apparmor.d/cache.d/CACHEDIR.TAG': No such file or directory

So, could "apparmor_parser --purge-cache" avoid deleting /etc/apparmor.d/cache.d/CACHEDIR.TAG?

Changed in apparmor (Debian):
status: Confirmed → Fix Released
intrigeri (intrigeri)
Changed in apparmor (Debian):
importance: Unknown → Undecided
status: Fix Released → New
summary: - apparmor_parser with --write-cache should not delete CACHEDIR.TAG
+ apparmor_parser with --write-cache and --purge-cache should not delete
+ CACHEDIR.TAG
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.