Compatibility with directives setting a different ssh-agent.

[Msouza91]

I use 1password and it has a feature to act my ssh-agent, I have my private keys saved there encrypted.
To enable that I have a rule atop of my ~/.ssh/config to ask ssh to use that agent to fetch keys, that is triggering the unrecognized character error some other people have mentioned.

The entry in question is:

Host *
  IdentityAgent "~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock"
it gets me the error:

Error: Failed to parse SSH configuration file: SshConfig(InvalidInclude(InvalidIncludeError { line: "", details: HostsInsideHostBlock }))

Not sure if it is the space between words on the Group Containers directory or the quotation marks to solve for said space in the path, but it doesn't work for me at the moment, unless I revert to the standard way of having the private keys unencrypted using the default ssh agent. I have a hunch is it not being able to handle the spaces since I have seen another issue where removing spaces from the Host part of the declaration worked around this issue for another user.

Is it a technical blocker impeding escaping the space hidden characters in the parser? Why should that be an issue if the path is inside double quotes to denote that the space is literal?

[Msouza91]

Having another look at issues and testing removing the characters, the issue might be related to sshs maybe not recognizing the IdentityAgent directive?

[quantumsheep]

Hey! Which version of sshs are you using? In the last version this should not happen.

sshs --version