Releases: bus1/dbus-broker
Releases · bus1/dbus-broker
dbus-broker-16
dbus-broker - Linux D-Bus Message Broker
CHANGES WITH 16:
* Explicitly mention our mailing-list in the README:
https://groups.google.com/forum/#!forum/bus1-devel
All dbus-broker releases are announced there, and the list is open
for any dbus and dbus-broker related discussions.
* Revert the removal of the --verbose switch of bus launcher. There
are existing users that pass this switch, and now suddenly fail
spawning dbus-broker. The switch is now a no-op and silently ignored.
* The global resource limits were reconsidered and aligned with the
values used by dbus-daemon(1) and current distributions. Furthermore,
the limits provided in the bus XML configuration are now interpreted
by the launcher and converted to the broker-internal accounting
scheme.
Contributions from: Daniel Rusek, David Herrmann, Marc-Antoine
Perennou, Tom Gundersen
- Tübingen, 2018-10-09
dbus-broker-15
dbus-broker - Linux D-Bus Message Broker
CHANGES WITH 15:
* Fix dbus-broker-launch to retain CAP_AUDIT_WRITE in its ambient
capability set, so dbus-broker will get it as well.
* Be less verbose about unknown usernames in the XML config of
dbus-broker-launch.
Contributions from: David Herrmann, Tom Gundersen
- Tübingen, 2018-08-08
dbus-broker-14
dbus-broker - Linux D-Bus Message Broker
CHANGES WITH 14:
* The broker now implements the org.freedesktop.DBus.Peer, and
org.freedesktop.DBus.Properties interfaces.
* The man-pages have been updated to reflect the current state of
dbus-broker and dbus-broker-launch.
* Matches are now indexed by all major fields, greatly improving
broadcast performance.
* The launcher now respects the `<user>NAME</user>' configuration and
correctly drops privileges of the broker and itself after startup.
* The `send_broadcast', `min_fds', and `max_fds' XML policy attributes
are now supported (as defined by dbus-daemon(1)).
* Configuration files are now watched for modifications by the
launcher. Any modification triggers a configuration reload. This
follows the behavior of dbus-daemon(1).
* The broker gained a `--machine-id' command-line switch to specify the
local machine-id to be served via the org.freedesktop.DBus.Peer
interface. The launcher uses libsystemd-daemon to provide it.
* The controller interface of dbus-broker has been renamed from
org.bus1.DBus.Launcher to org.bus1.DBus.Controller.
Contributions from: David Herrmann, Khem Raj, Tom Gundersen
- Tübingen, 2018-07-03
dbus-broker-13
dbus-broker - Linux D-Bus Message Broker
CHANGES WITH 13:
* The --verbose command-line switch was dropped from both the broker
and the launcher. Its behavior is now the default.
* Fix a startup dead-lock with systemd NSS plugins. This requires
setting the SYSTEMD_NSS_BYPASS_BUS environment variable, so
libnss_systemd.so will skip recursive bus-calls.
* Read /etc/{passwd,groups} early on from the launcher to
pre-initialize the nss-cache. This allows startup on properly
configured systems without ever calling into NSS. Furthermore, in
case this does not resolve all required usernames, the launcher will
loudly log any call into NSS, to better debug early dead-locks in bus
startup code.
Note that this new mechanic overrules /etc/nsswitch.conf for the
launcher. However, this is only made based on the assumption that
if an entry is present in /etc/{passwd,groups}, it better be a valid
entry. If an entry is not present, the launcher will still correctly
call into NSS.
Contributions from: David Herrmann, Tom Gundersen
- Tübingen, 2018-04-23
dbus-broker-12
dbus-broker - Linux D-Bus Message Broker
CHANGES WITH 12:
* Building documentation is now optional. Use -Ddocs=true with meson
to build documentation. It is disabled by default.
* The compatibility launcher now namespaces transient systemd units
based on its own name on the scope-bus (i.e., the bus
dbus-broker-launch uses to ask systemd for activation of units). This
allows running private dbus-broker instances, while using transient
systemd-units on the scope-bus for activation. For instance, at-spi2
can use activated units that clash with the namespace of the session
or system bus.
* Several bug-fixes.
Contributions from: Daniele Nicolodi, David Herrmann, Tom Gundersen
- Tübingen, 2018-04-17
dbus-broker-11
dbus-broker - Linux D-Bus Message Broker
CHANGES WITH 11:
* Building now requires linux-api-headers>=4.13. We expect the
SO_PEERGROUPS socket-option to be defined in the kernel headers.
Older kernels are still supported at runtime, but at build-time you
need to provide recent headers.
* The build-system now supports a new meson configuration option,
called 'system-console-users'. It takes an array of user-names which
should be considered 'at-console' by dbus-broker-launch. These extend
the existing range based on [SYSTEMUIDMAX+1..-1[ with a list of
statically provided usernames.
This allows distributions to provide special system-users that need
to be considered as 'at-console'. Right now, this should be used for
users like 'gdm', which are system-users, but need static access to
the console. Note that these usernames must be reserved by the
distribution, but don't have to be present at runtime. The launcher
dynamically picks the usernames that it can resolve, and retries on
every reload.
* The policy-type of the dbus-broker API has been simplified. It is now
reduced to a policy-batch indexed by uids, in combination with a
policy-batch indexed either by gid or uid-range. Per peer, the broker
will only ever select one uid-batch, and all matching gid/uid-range
batches. Note that anything but the per-uid-batch is deprecated, and
exclusively meant for backwards compatibility.
This change only affects dbus-broker. The compatibility launcher was
adapted to use this new API. It still converts the policy as given by
the XML configuration in a compatible way to the simplified internal
representation.
* The launcher now requires an explicit --audit commandline option to
enable auditing. Before, it was deduced based on the passed scope.
You now have to pass it explicitly.
* The launcher now supports a `--config-file PATH` commandline option
to override the root configuration file, which is still deduced based
on the passed scope parameter.
* A path miscomputation in the XML <include> tags was fixed. They should
work as expected now.
* The <servicedir> XML tags are now properly supported. Before, they
were correctly parsed, but never actually sourced for input.
* The XDG_DATA_DIRS environment variable is now supported by the
launcher, according to the related xdg spec. Note that this only
affects the user-scope!
* The --listen parameter was dropped from the launcher. Only
socket-activation is supported now. If required, any parent process
should now create the listener socket themselves, and pass it in like
socket activation.
* As usual, a bunch of fixes and small improvements!
Contributions from: David Herrmann, Tom Gundersen
- Tübingen, 2018-02-21
dbus-broker-10
dbus-broker - Linux D-Bus Message Broker
CHANGES WITH 10:
* Fix RequestName() / ReleaseName() to send signals before their reply,
to match dbus-daemon behavior.
* Several bug-fixes, cleanups, and performance improvements.
Contributions from: David Herrmann, Tom Gundersen
- Tübingen, 2018-02-07
dbus-broker-9
dbus-broker - Linux D-Bus Message Broker
CHANGES WITH 9:
* A configuration reload of the launcher can now be triggered via its
managing systemd instance. The ExecReload= key is hooked up to
trigger a ReloadConfig() D-Bus call.
* The launcher now runs as 'Type=notify' systemd service type. This
closes a possible dead-lock during startup. Previously, there was a
chance of systemd itself connecting to D-Bus in a blocking manner,
before the launcher was ready. This might have resulted in the
launcher waiting on systemd, and thus dead-lock.
By running as 'Type=notify' systemd will wait for the launcher to be
ready before connecting to it.
* Activated units now inherit their user from the actual D-Bus service,
if provided. They used to be started as root, but now the 'User=' key
is properly honored.
Contributions from: David Herrmann, Marc-Antoine Perennou, Tom
Gundersen
- Tübingen, 2017-11-30
dbus-broker-8
* The launcher now uses instantiated systemd template units when
activating a service that has no associated systemd service file.
This allows services to stick around after being deactivated. It is
closer in behavior to the original service activation of dbus-daemon,
while still keeping them out of the dbus-broker environment.
* Audit is now only enabled when --audit is passed to dbus-broker. By
default, the launcher will pass it only for the system bus.
* The launcher now supports configuration reloading. When triggered, it
forces the launcher to reload the bus configuration and all service
files, and adjust the broker state. Note that not all modifiers can
be adjusted at runtime (e.g., you cannot change the user the broker
runs as). The set of modifiers that can be adjusted at runtime is the
same set that dbus-daemon(1) supports.
The reload operation can be triggered via a direct SIGHUP to the
launcher, or via the ReloadConfig() call on org.freedesktop.DBus.
* The AddListener() call on org.bus1.DBus.Broker no longer accepts the
policy filesystem path. It was a no-op since dbus-broker supports
parsing policies in the launcher.
dbus-broker-7
* More bugfixes for 32bit architectures.