The officially official Devuan Forum!

steve_v

Member

Registered: 2018-01-11

Posts: 646  

Re: UDisks2: Security Considerations

someone else’s posts

s/someone/something/g

Obvious wall of LLM-generated copy-pasta is obvious, and the arguments it makes are all either inane or inapplicable. Do you really think anyone here cares about the threat of "shadow IT", "unknown assets" or the rest of the corporate-drone buzzword-soup padding? We are shadow IT.

Many other boards have policies regarding AI generated content (usually "go away"), perhaps it's time for the same here?

Last edited by steve_v (Today 15:54:58)

---

Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.

igorzwx

Member

Registered: 2024-05-06

Posts: 486  

Re: UDisks2: Security Considerations

You seem to insist on your right to censor my posts.

fsmithred

Administrator

Registered: 2016-11-25

Posts: 2,826  

Re: UDisks2: Security Considerations

Igor,

If steve_v has censored any posts, they were his own, and there's a note showing that he edited them. He can't edit your posts. I can, and if I ever do, I will leave a note in that post saying so. If any of your posts were edited by another admin, I'm not aware of it.

fsmithred

igorzwx

Member

Registered: 2024-05-06

Posts: 486  

Re: UDisks2: Security Considerations

Censorship doesn't necessarily mean editing.  There are many ways to silence someone.

There are many subtle ways to discourage someone from posting on a forum — beyond outright censorship. Constant accusations, excessive moderation, personal attacks, or repeatedly questioning someone's intent can create a hostile environment that pushes people away.

Last edited by igorzwx (Today 16:53:19)

laurie_dev1

Member

Registered: 2026-01-31

Posts: 11  

Re: UDisks2: Security Considerations

It's possible to remove the D-Bus daemon and get a pretty lean desktop, but if you want every single part of it (e.g. libraries) gone, you'll pretty much have nothing to work with. I experimented with this in a VM, and it's pretty bleak if you do it. Dillo is the only "graphical" Web browser that actually does survive this purge.

There was/is an experimental Refracta ISO from the Beowulf era that removes as much D-Bus as possible, using SpaceFM with LXDE's panel in place of Xfce. Perhaps Fsmithred could upload it again for your curiosity.

I gave it a try with some input from that thread @fsmithred quoted.
I was able to run the xorg session using bspwm ok, pretty much left to terminal utilities for the most part unless you install programs using tk an the like.
Yes, dillo was a graphical web browser i could install, good old fltk.
gtk3 needs dbus libraries, not sure about gtk2, but seeing as gtk2 is being phased out, im probably out of luck there as well with binary installations.
As has been noted, one could probably build programs without dbus, i had a look into firefox but seeing as though it relies on a host of dependencies related to dbus and gtk3, one would probably have to build gtk3 without the need for dbus first then firefox without dbus, not sure if that would be even doable.
Maybe palemoon or basilisk gtk2 web browser versions could be built without dbus.
There was one browser called privacybrowser that didnt need dbus provided by debian but it wants to drag in a lot of kde/qt6 dependencies and from what ive read debian does not include support for security updates in stable in regards to the qt6-webengine.
https://bugs.debian.org/cgi-bin/bugrepo … ug=1057755

This was just an experiment btw, not something i would use in production or daily, I need a fully functioning web browser like firefox.

But yeah here is what i did to pin all the dbus packages, not sure if all of those packages are warranted to be pinned, but why not do it anyhow!

Package: dbus
Pin: release n=excalibur-security
Pin-Priority: -1

Package: dbus
Pin: release n=excalibur
Pin-Priority: -1

Package: dbus-system-bus-common
Pin: release n=excalibur-security
Pin-Priority: -1

Package: dbus-system-bus-common
Pin: release n=excalibur
Pin-Priority: -1

Package: dbus-x11
Pin: release n=excalibur-security
Pin-Priority: -1

Package: dbus-x11
Pin: release n=excalibur
Pin-Priority: -1

Package: dbus-bin
Pin: release n=excalibur-security
Pin-Priority: -1

Package: dbus-bin
Pin: release n=excalibur
Pin-Priority: -1

Package: dbus-daemon
Pin: release n=excalibur-security
Pin-Priority: -1

Package: dbus-daemon
Pin: release n=excalibur
Pin-Priority: -1

Package: dbus-session-bus-common
Pin: release n=excalibur-security
Pin-Priority: -1

Package: dbus-session-bus-common
Pin: release n=excalibur
Pin-Priority: -1

Package: libdbus-1-3
Pin: release n=excalibur-security
Pin-Priority: -1

Package: libdbus-1-3
Pin: release n=excalibur
Pin-Priority: -1

Last edited by laurie_dev1 (Today 22:49:47)

ralph.ronnquist

Administrator

From: Battery Point, Tasmania, AUS

Registered: 2016-11-30

Posts: 1,609  

Re: UDisks2: Security Considerations

Don't copy AI output to here, @igorzwx, or anyone.