lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a4c581d0610041350m40fbf75dj724ef5d9e0d12025@mail.gmail.com>
Date:	Wed, 4 Oct 2006 22:50:26 +0200
From:	"Alessandro Suardi" <alessandro.suardi@...il.com>
To:	"Jesper Juhl" <jesper.juhl@...il.com>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: removed sysctl system call - documentation and timeline

On 10/4/06, Jesper Juhl <jesper.juhl@...il.com> wrote:
> Hi,
>
> With recent kernels I'm getting a lot of warnings about programs using
> the removed sysctl syscal.
>
> Examples (after 5 min of uptime here) :
> root@...gon:/home/juhl# dmesg | grep "used the removed sysctl system
> call" | sort | uniq
> warning: process `dd' used the removed sysctl system call
> warning: process `ls' used the removed sysctl system call
> warning: process `touch' used the removed sysctl system call
>
> and more can be found...
>
>
> I'm not, as such, opposed to removing sysctl (and yes, I know what it
> is and what it does). What I am a little opposed to is that it is
> being removed on such short notice (unless I missed the memo) and that
> it is hidden inside EMBEDDED.
>
> I would like to propose that, at least for 2.6.19, it be default on
> (as it is now), not hide it in EMBEDDED where people usually don't go,
> some huge deprecation warnings be added, and that it then gets the
> usual 6-12months before being removed (did it already get that and I'm
> just slow?)...  ohhh, and correct the help text; it currently says
> "...Nothing has been using the binary sysctl interface for some time
> now so nothing should break if you disable sysctl syscall support" -
> that's obviously false as demonstrated by the above extract from my
> dmesg...

Another data point then... this is FC5-uptodate:

[asuardi@...dman incoming]$ dmesg | grep -i sysctl
warning: process `date' used the removed sysctl system call
warning: process `touch' used the removed sysctl system call
warning: process `salsa' used the removed sysctl system call

--alessandro

"Well a man has two reasons for things that he does
  the first one is pride and the second one is love
  all understandings must come by this way"

     (Husker Du, 'She Floated Away')
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ