Originally posted by JS987
View Post
Announcement
Collapse
No announcement yet.
KDBUS & Systemd Now Yields A Working System
Collapse
X
-
Originally posted by RahulSundaram View PostThat isn't a very useful comment since kernel developers have explained precisely how it does improve security and I have already linked to thatLast edited by JS987; 27 December 2013, 05:51 PM.
Comment
-
Originally posted by RahulSundaram View PostThat isn't a very useful comment since kernel developers have explained precisely how it does improve security and I have already linked to that
https://lwn.net/Articles/551969/
Comment
-
Originally posted by zester View PostThere full of shit, and to prove it the following statement is laughable at best "It chose D-Bus because it is well-documented, well-understood" <-- That's why most people use ZeroMQ IPC/INPROC with Google Protobuf. Also kdbus was a student project that was rejected once before, it was then abandoned. This is all about Greg Kroah-Hartman and what he wants.
Comment
-
Originally posted by JS987 View PostSecurity hole in kernel code can have bigger impact than security hole in user space code. Kernel developers don't really care about security.
Comment
-
Originally posted by RahulSundaram View PostSo many factual inaccuracies in so few sentences. The current kdbus project was written from scratch and no student was involved in it and what if they were? Even Linux kernel was written by a student in the first place! D-Bus is the most widely used IPC system in Linux and installed by default in most Linux systems far more than any ZeroMQ or Google Protobuf, neither of which are even really comparable. Also current development of kdbus isn't done by Greg KH at all. If you have done any IPC programming, your comments would make more sense.
D-Bus doesn't even come close to ZeroMQ is usage share not even close.
Even when comparing D-Bus vs ZeroMQ in the IPC arena for every one D-Bus Desktop application there is 1000+ ZeroMQ network applications using its native IPC there.
Go take your fanboy bullshit someplace else.
Comment
-
Originally posted by RahulSundaram View Postkdbus is a simpler protocol than dbus-daemon and integration with things like namespaces only help with better security. Kernel security isn't a binary thing and sometimes userspace can have a much bigger impact than kernel bugs. It really depends on what kind of security hole it is. For instance, BIND bugs caused havoc a few years back more than any Linux kernel issue ever did. While Linux kernel security could certainly better, it is very much incorrect to claim that kernel developers don't care about security. Some developers work on it very diligently including say Kees Cook, Dan, James Morris and several others. The solution isn't to hide your head in the sand. It is to provide the functionality that developers need and IPC mechanisms are pretty core to what is needed for Linux as a platform.
Comment
-
Originally posted by zester View PostWell I would hope it was a simpler api lol, full on D-Bus sitting in the kernel would be insane. Ummmm IPC and Security don't compute sorry IPC is anti-security by default, not saying we shouldn't use it but to putting it in the kernel on a system that isn't locked down is stupid. And kdbus's api is odd and still overly complex for something so sensitive to kernel security.
Comment
Comment