tree 20c440fa8d3c2a8dbd37fa060a6d7cf7eeeb989c
parent 41a309aa54156025311b2f3a678281d804a3b615
author Daniel Erat <derat@chromium.org> 1531962470 -0700
committer chrome-bot <chrome-bot@chromium.org> 1532056374 -0700

tlsdate: Let tlsdated send to its own D-Bus interface.

org.torproject.tlsdate.conf contains the following stanza:

  <policy context="default">
    <deny send_interface="org.torproject.tlsdate" />
    ...
  </policy>

This appears to apply to the "tlsdate" user that's used to
run tlsdated. For reasons that are unclear to me, with this
stanza, I'm able to observe TimeUpdated D-Bus signals when
running dbus-monitor as the root user, but Chrome doesn't
receive them. It's not clear to me if this behavior is
deterministic or whether it's changed over time.

This change adds an "allow send_interface" directive to the
user="tlsdate" stanza at the top of the file, which results
in Chrome receiving TimeUpdated signals as expected.

BUG=chromium:860442,chromium:661205
TEST=made chrome log when receiving TimeUpdated and verified
     that signals are received at boot for "system-clock"
     and "network"

Change-Id: I36950a5da78fd18fcb3883b088f60d641d2bddb8
Reviewed-on: https://chromium-review.googlesource.com/1142825
Commit-Ready: Dan Erat <derat@chromium.org>
Tested-by: Dan Erat <derat@chromium.org>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>