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] [day] [month] [year] [list]
Message-ID: <CANszf4jU4m2E74vvd2aa7eu8vf3q8iKEdXTYR3N3XBwLQdowtw@mail.gmail.com>
Date:	Mon, 22 Jun 2015 12:47:49 +0100
From:	Rogelio Serrano <rogelio.serrano@...il.com>
To:	Martin Steigerwald <martin@...htvoll.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: careful review of kdbus

On Sat, Jun 20, 2015 at 11:17 AM, Martin Steigerwald
<martin@...htvoll.de> wrote:
> Hello!
>
> In the light of
>
>         * kdbus support is no longer compile-time optional. It is now
>           always built-in. However, it can still be disabled at

a patch to remove all of that code would be welcome...

>           runtime using the kdbus=0 kernel command line setting, and
>           that setting may be changed to default to off, by specifying
>           --disable-kdbus at build-time. Note though that the kernel
>           command line setting has no effect if the kdbus.ko kernel
>           module is not installed, in which case kdbus is (obviously)
>           also disabled. We encourage all downstream distributions to
>           begin testing kdbus by adding it to the kernel images in the
>           development distributions, and leaving kdbus support in
>           systemd enabled.
>
> Lennart Poettering: [systemd-devel] [ANNOUNCE] systemd v221
> http://lists.freedesktop.org/archives/systemd-devel/2015-June/033170.html
>
> I hope you kernel developers will still review kdbus carefully as you did so
> far, instead of giving in to any downstream pressure by distros.
>
> It is exactly this attitude and this approach of systemd upstream that I
> feel uneasy about. Instead of humbly waiting and working towards having
> kdbus accepted to the kernel, systemd developers seem to use any means to
> create indirect pressure to have it included eventually.
>
> I hope that it will still be technical excellence as entry barrier for
> anything that goes into the kernel.
>
> Please note: I do not judge upon the technical quality of kdbus. I think
> others are more knowledgeable to do it.
>
> Thank you,
> --
> Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
> GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> Please read the FAQ at  http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ