For users who run tensorboard on a multi-user host (e.g., on a shared compute server, or HPC cluster as in this example), it would be beneficial for security to allow tensorboard to bind to a Unix domain socket (instead of a TCP port). File permissions on the socket file could be set to allow access only by the user that created it, and the user could securely access their tensorboard session on the remote host via Unix domain socket forwarding (which OpenSSH has supported since v6.7).
The Werkzeug dev server supports listening on a unix domain socket.
For users who run tensorboard on a multi-user host (e.g., on a shared compute server, or HPC cluster as in this example), it would be beneficial for security to allow tensorboard to bind to a Unix domain socket (instead of a TCP port). File permissions on the socket file could be set to allow access only by the user that created it, and the user could securely access their tensorboard session on the remote host via Unix domain socket forwarding (which OpenSSH has supported since v6.7).
The Werkzeug dev server supports listening on a unix domain socket.