Use of tunnelProtocol header in sandcat fails

[timbrigham-oc]

Describe the bug
When adding headers for the creation of sandcat executable, the "tunnelProtocol" value is not respected.

To Reproduce
Steps to reproduce the behavior:
First create a Windows agent using the standard caldara header syntax:

$wc=New-Object System.Net.WebClient;
$wc.Headers.add("platform","windows");
$wc.Headers.add("file","sandcat.go");
$wc.Headers.add("server","https://127.0.0.1:8443");
$wc.Headers.add("group","redSSL");
$wc.Headers.add("tunnelAddr","x.x.x.x:8022");
$wc.Headers.add("tunnelUser","sandcat");
$wc.Headers.add("tunnelPassword","xxxxxxxxx");
$wc.Headers.add("tunnelProtocol","SSH");

Then launch the client in verbose mode:

& C:\test.exe -v
Starting sandcat in verbose mode.
[*] No tunnel protocol specified. Skipping tunnel setup.
[*] Attempting to set channel HTTP
Beacon API=/beacon

Expected behavior
The addition of a header value should substitute for for a command line argument.

Desktop (please complete the following information):
Happens on Win 10, Win11. Current latest build.

[github-actions]

Looks like your first issue -- we aim to respond to issues as quickly as possible. In the meantime, check out our documentation here: http://caldera.readthedocs.io/

[github-actions]

This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days