Re: Bug#622922: ITP: apparmor -- AppArmor Mandatory Access Control system userspace tools

To: Ben Hutchings <ben@decadent.org.uk>
Cc: debian-devel@lists.debian.org
Subject: Re: Bug#622922: ITP: apparmor -- AppArmor Mandatory Access Control system userspace tools
From: Joachim Wiedorn <ad_debian@joonet.de>
Date: Sat, 16 Apr 2011 19:58:23 +0200
Message-id: <[🔎] 20110416195823.09d9bb5e@jupiter.home>
In-reply-to: <[🔎] 1302966673.5282.843.camel@localhost>
References: <20110415212431.10699.4466.reportbug__47432.9315744855$1302905010$gmane$org@localhost6.localdomain6> <[🔎] slrniqiulq.36f.trash@kelgar.0x539.de> <[🔎] 1302966673.5282.843.camel@localhost>

Ben Hutchings <ben@decadent.org.uk> wrote on 2011-04-16 16:11:

> I'm (slowly) working on a way to build in all LSMs and then free memory
> for those that aren't used.

That is a good news because I am on the way to package smack tools for
Debian.

---
Have a nice day.

Joachim (Germany)

Reply to:

References:
- Re: Bug#622922: ITP: apparmor -- AppArmor Mandatory Access Control system userspace tools
  - From: Philipp Kern <trash@philkern.de>
- Re: Bug#622922: ITP: apparmor -- AppArmor Mandatory Access Control system userspace tools
  - From: Ben Hutchings <ben@decadent.org.uk>

Prev by Date: Re: Default size limits for /run (/var/run) and /run/lock (/var/lock)
Next by Date: /run or not /run?
Previous by thread: Re: Bug#622922: ITP: apparmor -- AppArmor Mandatory Access Control system userspace tools
Next by thread: Static libraries in development packages
Index(es):
- Date
- Thread