While the python-based AppArmor utils (aa-logprof etc.) are much easier to understand and maintain than the old perl code, there are still some terribly long functions like parseprofiledata() in aa.py that are not too easy to understand. Also, using hasher() (a recursive array) as storage can have some strange side effects. Another problem is that test coverage isn't too good, especially for the bigger functions.
I already wrote the CapabilityRule and CapabilityRuleset classes (and also the BaseRule and BaseRuleset classes) some months ago, and changed the code to use those classes. This code is already in upstream bzr.
My plan for hackweek is to convert more rule types into classes, and to add full test coverage for them. Besides much more readable code, this will also result in "accidently" fixing some bugs that were not noticed yet.
A side goal is to keep the upstream devs busy with patch reviews by continueing my patch flood I started some weeks ago *g*
I'll start with network rules / the NetworkRule and NetworkRuleset classes, and then maybe roll a dice to decide what I'll convert next ;-)
Looking for mad skills in:
apparmor python tests
This project is part of:
Hack Week 12
Let's make reposync faster
At SUSE we've implemented a module on Salt call...
As there is no progress around [MIrrorPinky](ht...
Following a FOSDEM presentation on [Angr](http:...
During the last year Askbot, a question and ans...