dbus-daemon(1): Be more truthful about the default policy

We don't allow sending unrequested replies, but the documentation
implied that we did.

Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: Thiago Macieira <thiago@kde.org>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=92853

diff --git a/doc/dbus-daemon.1.xml.in b/doc/dbus-daemon.1.xml.in
index 447b7fd..dcaba48 100644 (file)
--- a/doc/dbus-daemon.1.xml.in
+++ b/doc/dbus-daemon.1.xml.in
@@ -779,9 +779,13 @@ they are analogous to a firewall in that they allow expected traffic
 and prevent unexpected traffic.</para>
 
 
-<para>Currently, the system bus has a default-deny policy for sending method calls
-and owning bus names.  Everything else, in particular reply messages, receive
-checks, and signals has a default allow policy.</para>
+<para>
+  Currently, the system bus has a default-deny policy for sending method calls
+  and owning bus names, and a default-allow policy for receiving messages,
+  sending signals, and sending a single success or error reply for each
+  method call that does not have the <literal>NO_REPLY</literal> flag.
+  Sending more than the expected number of replies is not allowed.
+</para>
 
 
 <para>In general, it is best to keep system services as small, targeted programs which