[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#336561: marked as done (linux-image-2.6: CONFIG_SECURITY_CAPABILITIES=y prevents)

Your message dated Sat, 11 Mar 2006 22:38:34 +0100
with message-id <20060311213834.GC25190@wavehammer.waldi.eu.org>
and subject line Bug#336561: linux-image-2.6: CONFIG_SECURITY_CAPABILITIES=y prevents realtime-lsm and dazuko being used with a stock kernel
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.14-1-686
Version: 2.6.14-1
Severity: normal
Tags: patch

Hi, I tried to build the realtime-lsm against 2.6.14 and it complained 
that it couldn't do so unless CONFIG_SECURITY_CAPABILITIES was built 
into the kernel as a module.



I'm just about to try installing the realtime-lsm against a kernel 



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-1-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.14-1-686 depends on:
ii  module-init-tools             3.2-pre9-3 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.11-9   Yet Another mkInitRD

linux-image-2.6.14-1-686 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On Sat, Mar 11, 2006 at 10:17:42PM +0100, Florent Bayle wrote:
> I'm taking over the Dazuko package, and it needs 
> "CONFIG_SECURITY_CAPABILITIES" set as module. According to the faq of Dazuko, 
> it's because : "the "capability" module does not support stacking" [1] [2].

This is incorrect. As already said, it is possible to disable the
compatibility module completely on request, just do that.

The parameter is capability.disable=1.


Those who hate and fight must stop themselves -- otherwise it is not stopped.
		-- Spock, "Day of the Dove", stardate unknown

Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: