commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DAEMON-168) [daemon][jsvc] Handling of capabilities should use libcap
Date Mon, 02 Aug 2010 19:55:18 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mladen Turk updated DAEMON-168:
-------------------------------

    Fix Version/s: 1.0.3
                       (was: 1.0.2)

> [daemon][jsvc] Handling of capabilities should use libcap
> ---------------------------------------------------------
>
>                 Key: DAEMON-168
>                 URL: https://issues.apache.org/jira/browse/DAEMON-168
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Jsvc
>    Affects Versions: 1.0.2
>         Environment: Debian Unstable
>            Reporter: Damien Raude-Morvan
>             Fix For: 1.0.3
>
>         Attachments: old_capabilities.diff
>
>
> Hi,
> [For full story, please see here : http://bugs.debian.org/412690]
> As 1.0.2 release, jsvc component use a syscall to handle capabilities settings.
> Here is an example in src/native/unix/native/jsvc-unix.c:
>   if (syscall(__NR_capset, &caphead, &cap) < 0) {
> It's not recommended usage of capabilities since ABI/API can change at each kernel release.
> And in fact, it's already changed and kernel handle some backward compat layer like described
here :
> http://marc.info/?l=linux-kernel&m=120883245227970&w=2
> For now, I'm forced to patch jsvc to force usage of the backward compatibility layer.
> (see attached patch)
> Cheers,
> -- 
> Damien Raude-Morvan

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message