ulterno

OOP can now confidently check the "I'm not a robot" checkbox.

Isn't that a bit more than 20 years ago?

Also, Green on Black is subjectively better than White on Blue.

On one hand, I thought of policies as the correct way to do stuff, since the user (root) then gets to decide who gets what.
But considering the lack of good enough defaults and that most users won't even know where to look at, I guess we do need additional security features in this case.

For once, it would be good to find a way to reliably let a process (providing said endpoint) know which other process is trying to access said endpoint. This, combined with the root locations (like /bin, /usr/bin etc.) not being writeable without root privileges, should make it possible to have adequate security options in the program itself.

So, they were psychopaths who realised they could go unnoticed even more easily if they just took up the religion?

I absolutely hate that character. So much that I had to drop the otherwise, mildly interesting series.

You worded it better than I would ever have.

You are thinking too hard.
Just projectile him into position.

vaxry talked about LD_PRELOAD and I feel like that is a non-issue in this case.
If an attacker has the ability to modify LD_PRELOAD of an application, they already an ability to modify its behaviour without depending upon what D-Bus may let it do.
And if the attacker can change LD_PRELOAD for a process running as root, they might as well affect the target service directly rather than try doing something with the dbus daemon.

severe security flaws in D-Bus

I searched for this and all I got was CVEs in the implementations.
What are the flaws in the protocol that I don't know of? If you can link it, I would love to read.

I recently started interacting with code that had something to do with D-Bus and from what I saw, there were policy files, which are required to do anything with D-Bus endpoints provided by software. That's essentially where I stopped, considering that to be the end-all for D-Bus security.

What am I missing?

Might as well rewrite Shakespeare in Rust, while we are at it :P

prove their worth out of tree until some sort of coherent best practices are established

I feel like this is what the Technical Advisory Board should be replying with.