Should TR binaries (tids, tidc, trust_router) unset DISPLAY themselves in their invoked environments?

[Stefan Paetow]

Given that the classic problem of the DISPLAY variable being passed (somehow, somewhere, don't ask me how) along into the environment that TIDC (and the TID library), TIDS and TRUST_ROUTER consume crops up time and again, can we perhaps get those binaries to sanitize their environment to explicitly UNSET the DISPLAY variable to avoid credential retrieval from failing?

We *know* those binaries will always be invoked from a non-X environment, so why don't they simply make sure DISPLAY is not set to avoid unfavourable interactions with DBUS and X?