wolfpld
Implement verification of server
Usage of Tracy on public machines can be dangerous since another Tracy's user can catch client session and theoretically get a control on execution of client code. So, it would be nice to have an ability to verify that is a proper server.
One of the solution is to provide TRACY_PASSWORD env var both for client and server and compare them at client side.
You can achieve this by restricting bind address to localhost, and then forwarding ports via ssh.
What if I'm not a single user of localhost? For example, it can be a login node of HPC cluster
I'm not saying the password idea is not worth investigating, just providing solutions you can use right at this moment.