Bus authentication on Windows
nesuan23 at gmail.com
Sat Dec 26 01:19:57 PST 2015
On Linux, clients *know* that the system bus is actually controlled by
the system administrator because of appropriate file permissions (unix
domain sockets) or a privileged TCP port number (<1024).
On Windows, the only supported transport is TCP, however Windows allows
any user to bind to any TCP port. So how does a client verify that the
bus it connects to is actually controlled an administrative process and
not some other hostile user who has 'hijacked' the TCP port and is
masquerading as the real bus in order to sniff traffic?
More information about the dbus