mirror of
https://gitlab.freedesktop.org/dbus/dbus.git
synced 2025-12-26 15:40:09 +01:00
cfd73beacf
This is an interpretation of the existing text. There are two plausible ways a relaying server could interpret "must ignore [new] fields": it could pass them through as-is, or it could delete them before relaying. Until now, the reference implementation has done the former. However, this behaviour is difficult to defend. If a server relays messages without filtering out header fields that it doesn't understand, then a client can't know whether the header field was supplied by the server, or whether it was supplied by a (possibly malicious) fellow client. We can't introduce useful round-trip-reducing header fields like SENDER_UNIX_USER_ID or SENDER_LINUX_SECURITY_LABEL until the message bus filters them out, *and* provides a way for clients to know for sure that it has done so. This is a step towards that feature. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=100317 Reviewed-by: Philip Withnall <withnall@endlessm.com> Signed-off-by: Simon McVittie <smcv@collabora.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| busconfig.dtd | ||
| dbus-api-design.duck | ||
| dbus-cleanup-sockets.1.xml.in | ||
| dbus-daemon.1.xml.in | ||
| dbus-faq.xml | ||
| dbus-launch.1.xml.in | ||
| dbus-monitor.1.xml.in | ||
| dbus-run-session.1.xml.in | ||
| dbus-send.1.xml.in | ||
| dbus-specification.xml | ||
| dbus-test-plan.xml | ||
| dbus-test-tool.1.xml.in | ||
| dbus-tutorial.xml | ||
| dbus-update-activation-environment.1.xml.in | ||
| dbus-uuidgen.1.xml.in | ||
| dcop-howto.txt | ||
| diagram.png | ||
| diagram.svg | ||
| doxygen_to_devhelp.xsl | ||
| file-boilerplate.c | ||
| introspect.dtd | ||
| introspect.xsl | ||
| Makefile.am | ||
| system-activation.txt | ||
| TODO | ||
