It is actually the only good and properly working solution.
And the problem with localization is one reason, beside its not a SSH problem, why it isn't part of any SSH library.
The environment differs on every machine and the developer on the client side has to ensure it works.
Nobody knows how all programs ask for credentials.
One is asking "Username", another "Login" or "EMail", "Password", "Auth" and so on.
You have to accept this is not "Hello World hacking". Automation or interaction with 3rd party software is never an
easy task.
So pining the environment your app is working in, is the only solution.
At least SSH.Net gives you the freedom to accomplish this task and thats good.
And the problem with localization is one reason, beside its not a SSH problem, why it isn't part of any SSH library.
The environment differs on every machine and the developer on the client side has to ensure it works.
Nobody knows how all programs ask for credentials.
One is asking "Username", another "Login" or "EMail", "Password", "Auth" and so on.
You have to accept this is not "Hello World hacking". Automation or interaction with 3rd party software is never an
easy task.
So pining the environment your app is working in, is the only solution.
At least SSH.Net gives you the freedom to accomplish this task and thats good.