Skip to content
This repository was archived by the owner on Sep 27, 2024. It is now read-only.

Can't connect to remote host when running scap-workbench on Windows #305

@tylerjharden

Description

@tylerjharden

I receive this issue/error in the Diagnostics window, it is apparent that the bundled SSH executables are trying to write/read to Unix file paths, and there is no documentation or configuration to modify this behavior.

I reviewed several issues that appeared similar, one mentioning that a system restart resolved the problem, but that did not remediate my issue.

Can't connect to remote machine! 
Exception was: There was a problem with SshConnection! Failed to create SSH master socket!
Diagnostic info: Starting process 'ssh.exe -M -f -N -o ServerAliveInterval=60 -o ControlPath=C:/Users/REDACTED~1/AppData/Local/Temp/ci3k1z/ssh_socket -p 22 REDACTED@REDACTED' 
Starting process 'ssh.exe -M -f -N -o ServerAliveInterval=60 -o ControlPath=C:/Users/REDACTED~1/AppData/Local/Temp/ci3k1z/ssh_socket -p 22 azureuser@REDACTED' 

stdout: 
=============================== stderr: =============================== 
Could not create directory '/home/REDACTED/.ssh'. Failed to add the host to the list of known hosts (/home/REDACTED/.ssh/known_hosts). \S Kernel \r on an \m Permission denied (publickey). 

Working in a classified environment so the remote system IP and my Azure AD/Windows User Name are redacted accordingly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions