The daemon is called out to every time a device authenticates with a remote device, and encrypts a message. The daemon should be profiled to determine if it is adding a non-trivial overhead to communication latency (if it is, we'd want to migrate the code to third_party/ and call it directly).

(assigning to myself and upping priority, as a part of a broader effort to improve Smart Lock performance)