Package: libcap2
Version: 2.09-1
Severity: wishlist

Linux 2.6.25.6 has the following in kernel/capability.c:

--8<---------------cut here---------------start------------->8---
/*
 * Version 2 capabilities worked fine, but the linux/capability.h file
 * that accompanied their introduction encouraged their use without
 * the necessary user-space source code changes. As such, we have
 * created a version 3 with equivalent functionality to version 2, but
 * with a header change to protect legacy source code from using
 * version 2 when it wanted to use version 1. If your system has code
 * that trips the following warning, it is using version 2 specific
 * capabilities and may be doing so insecurely.
 *
 * The remedy is to either upgrade your version of libcap (to 2.10+,
 * if the application is linked against it), or recompile your
 * application with modern kernel headers and this warning will go
 * away.
 */

static void warn_deprecated_v2(void)
{
        static int warned;

        if (!warned) {
                char name[sizeof(current->comm)];

                printk(KERN_INFO "warning: `%s' uses deprecated v2"
                       " capabilities in a way that may be insecure.\n",
                       get_task_comm(name, current));
                warned = 1;
        }
}
--8<---------------cut here---------------end--------------->8---

The result is that with zsh, my login shell, being linked against
libcap2, I get this warning on the first login.  Would be nice if you
could package libcap2 2.10 which, according to the comment above, should
remedy this.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25.6
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libcap2 depends on:
ii  libc6                         2.7-12     GNU C Library: Shared libraries

libcap2 recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to