On Mon Mar 4, 2024 at 9:13 AM CET, Werner Koch wrote: > Because all components of gnupg will start gpg-agent and the other > daemons oin the fly and make sure that only one is started.
Do I understand it correctly that gnupg contains smaller version of systemd (dependency activation) inside of itself and that clashes with systemd? Is there some way how to switch it off and to make individual parts of gnupg behaving just The Unix Way™, do one thing (cryptographic operations, gpg-agenting or whatever) and do it well? > I have no idea what this is about. In case you need to play interesting > games with the sockets, the gpgconf.ctl mechanism might be helpful. MicroOS by openSUSE (and Fedora Atomic and many others, every Linux distro has its own variant of this, I guess) are container-oriented systems, where only minimal host system is used to run multiple isolated containers (Docker/Podman, distrobox, or Flatpak). SELinux and other methods are used to keep these containers isolated from the host system and one from another, sockets are under proper circumstances accessible. > Using no-autostart in the common.conf might be useful. We use it always > when running a remote gpg. That looks interesting, I will look into that. Best, Matěj -- http://matej.ceplovi.cz/blog/, @mcepl@floss.social GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Ludwig Boltzmann, who spent much of his life studying statistical mechanics, died in 1906, by his own hand. Paul Ehrenfest, carrying on the work, died similarly in 1933. Now it is our turn to study statistical mechanics. -- David L. Goodstein “States of Matter”
E09FEF25D96484AC.asc
Description: application/pgp-keys
signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
