New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support SSH Include
directive
#51
Conversation
I've created a post in the forum but it looks like it requires admin approval. |
Can you re-post your change against the Also note that on the "dev" branch, there's |
For some reason, WinSCP won't build anymore with the dev branch. I've already re-built all dependencies but got no luck.
You can take my changes and rebase them on the dev branch, no problem if there's no attribution. I also don't know how I should handle
|
I guess you didn't rebuilt the neon library. In WinSCP 6.1 (OpenSSL 3.1), the |
I just tested it again and I noticed that lib files were not copied in source\Win32 folder automatically. I did it manually and got it compiling. Thanks for the tip
What about the third question? Should I return null? Should I throw something? Should I skip this case? |
Sorry, I missed your question. I do not think you need to do anything. Parsing of the directives is out of scope of the |
cb62901
to
8b0ed40
Compare
8b0ed40
to
8710eab
Compare
I rebased on dev branch. I had to edit |
While OpenSSH indeed resolves |
My updates: |
This PR adds support for parsing of
Include
directive used in ssh config file during the sites import process