Package: debian-policy
Version: 3.2.1.0
I have coded a partial solution to this problem before I read this bug. it's
not as nice as a start-rc.d script, but it IS simpler (OTH, it requires more
code to be added in the postinst scripts, and it's a less generic solution).
I can, however, write a st
http://www.kernel.org/pub/linux/libs/security/linux-privs/
has some info, the README has some pointers as well.
/usr/include/linux/capability.h is well commented and tells you the
different capabilities that are available.
Britton Kerin
On Fri, 22 Sep 2000, Jonathan D. Proulx wrote:
> Hi,
>
> > But anyway, capabilities are useable without fs support.
>
> Definitely. Some daemons like proftpd already use them.
>
> Also, keep in mind that the set of capilities differs between 2.2 and
> 2.4 kernels if memory serves me correctly, and people are still looking
> at making sure the curren
Brian May <[EMAIL PROTECTED]> writes:
> Personally (and I realize others do disagree), my feeling is:
>
> - Kerberos 4 is obsolete and should not be used anymore. MIT no longer
> support it. There is only one mainstream application that still
> requires Kerberos 4: AFS. It could be argued that A
> it means that very rarely can Build-Depends-Indep used, and also
> that build daemons building only architecture-dependent parts of the
> package need often install also everything needed to build the
> architecture-independent parts. This is not good.
Right.
> However, to make use of the prop
> "Greg" == Greg Stark <[EMAIL PROTECTED]> writes:
Greg> That would be clean, but it's not practical, in this case
Greg> I'm talking about kerberos and /etc/krb.conf and
Greg> /etc/krb.realms. These files are standardized upstream and
Greg> we can't start moving them around.
I
6 matches
Mail list logo
