As of now we rely on host logs to trace problems with security key message forwarding, I think it would be faster if the remote_security_key binary had some troubleshooting capabilities for common configuration issues.

I think we should add a debug commandline param which:
1.) Checks the path for the binary in the registry
2.) Checks the Chrome Policy for security key
3.) Checks for the existence of the IPC channel
4.) If 3 works, then it could try connecting and sending a test message which would act as a loopback test.