guardctrl remote needs better way to get env var settings
When guardctrl is setup for remote access through ssh ForceCommand, there's not currently a good way to get the guardctrl binary the needed env vars (IFO, GUARD_MODULE_PATH) other than through a wrapper script. Should guardctrl just read /etc/guardian/local-env directly?