On Wed, 29 Jul 2020 18:37:55 +0200 Christian Boltz <[email protected]> wrote:
> Hello, > > I just noticed that this mail about the aa-status changes never made > it to yast-devel, probably because John isn't subscribed there. > > Is this mail with the json examples "good enough", or do you want/need a > bugreport to track this? Hi Christian, bug report is better so we can properly plan for it and it is also has history when/if we need more details about change. Thanks Josef > > FYI: AppArmor 3.0 will be released soon[tm], so please don't wait too > long with adjusting the YaST side. > > > ---------- Weitergeleitete Nachricht ---------- > > Betreff: Re: [apparmor] [yast-devel] Upcoming changes in AppArmor aa-status > output > Datum: Mittwoch, 10. Juni 2020, 16:40:50 CEST > Von: John Johansen <[email protected]> > An: Stefan Hundhammer <[email protected]>, Christian Boltz > <[email protected]> > Kopie: [email protected], [email protected] > > On 5/4/20 1:08 AM, Stefan Hundhammer wrote: > > On 2020-04-30 13:22, Christian Boltz wrote: > >> Hello, > >> > >> AFAIK the YaST AppArmor module uses the JSON output of aa-status. > >> > >> There are two upcoming changes, and I'd like to point them out so that > >> you can adjust the YaST AppArmor module if needed. > > > > This time PLEASE remember to also bump the JSON version number of > > that output. We had to do a pretty ugly hot fix for that last time, > > and it was just coincidence that this did not conflict with the > > previous version. > > > > the JSON version was bumped to 2 > > attached is an example output of aa-status, along with the corresponding > pretty json and compressed json output using the new unconfined, kill, > mixed, and prompt modes > > ------------------------------------------------------------- > > > > Regards, > > Christian Boltz -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
