dbus suspicious activity

[LINK]

Hello everyone, my name is LINK. The thing is, in CorePure64 or maybe also in the rest of the branches, when installing any browser, it also installs, dbus with its dependencies as elogind, which I find extremely strange and frustrating, since the dbus-launch --autolaunch process appears. I'm not an expert on dbus, but I'm worried that it's not on the dependency list, but it is dep. and the program doesn't run without it...

I also noticed that even wireshark, yad, librewolf etc. dbus also have an unspecified dependency. As far as I know, with dbus it is quite possible to organize file sharing with a remote machine, as well as full host management.

 Sorry for my English.   

[GNUser]

Hi LINK. yad doesn't require dbus, but will start dbus if dbus is available on the system. To prevent yad from starting dbus you can create a wrapper script (e.g., /home/tc/.local/bin/yad) that looks like this:

Code: [Select]

#!/bin/sh
export NO_AT_BRIDGE=1
exec /usr/local/bin/yad "$@"Note that .dep files are recursive. gtk3.tcz and gtk2.tcz both have dbus.tcz in their dependency tree. If application foo depends on gtk3.tcz and dbus.tcz, foo.tcz.dep will contain gtk3.tcz but not dbus.tcz.

In my experience, many gtk applications depend on dbus and will start it if it's not already running. I think this is normal and not anything malicious.

[CardealRusso]

librewolf was compiled --without-dbus, but as @GNUser stated, dbus is started by gtk. This is mentioned in the buildscript http://tinycorelinux.net/15.x/x86_64/tcz/src/librewolf/mozconfig
With pale moon, however, dbus is not started, even though it is a gtk2 dependency.

Here is a patchset for gtk3, which includes making dbus optional. https://github.com/lah7/gtk3-classic

[nick65go]

I like (and used in the past) the method exposed by GNUser. My actual aproach today is to have an easy accesible menu (in windows manager), or in PATH, for a fast run of a custom sh script: to on-demand kill all d-bus instance and its childern. Becasue you can kill a dbus process for a program (ex: firefox) but then a new program (that you install later) could start again dbus.

Or, if you like TC defaut scripts -- which auto-add/list "services/demons in a FLTK window/panel, like cron, udhpc --, then you or TC developers, can have them (d-bus) directly in core settings panel, that you can start/stop. You just need to folow the logic of how these services show-up in the list, having the proper scripts in proper destinations.
 

[LINK]

thank you for all your helpful answers! 

sh script: to on-demand kill all d-bus instance and its childern. Becasue you can kill a dbus process for a program (ex: firefox) but then a new program (that you install later) could start again dbus.

Destroying the dbus process will result in the program being closed.

librewolf was compiled --without-dbus, but as @GNUser stated, dbus is started by gtk. This is mentioned in the buildscript http://tinycorelinux.net/15.x/x86_64/tcz/src/librewolf/mozconfig
With pale moon, however, dbus is not started, even though it is a gtk2 dependency.

Here is a patchset for gtk3, which includes making dbus optional. https://github.com/lah7/gtk3-classic

that's right, it's strange that it's implemented this way, your advice with patches is interesting, thank you!

Note that .dep files are recursive. gtk3.tcz and gtk2.tcz both have dbus.tcz in their dependency tree. If application foo depends on gtk3.tcz and dbus.tcz, foo.tcz.dep will contain gtk3.tcz but not dbus.tcz.

In my experience, many gtk applications depend on dbus and will start it if it's not already running. I think this is normal and not anything malicious.

In other distributions, the same foo requiring dbus gtk3 are launched without the at-spi2-core dbus-launch etc. processes. Apparently, the problem is for me in the gtk3 package