-
Notifications
You must be signed in to change notification settings - Fork 148
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
Host keyword in ssh config should be case-insensitive #76
Comments
Hi @jsundmannorberg, Are you mostly concerned with treatment of the "Host" keyword itself? Or is handling other keywords important as well? While fixing the instance for the "Host" keyword you pointed out is a simple one-line change, there are other Thanks, |
Hi @norrisjeremy, The Host keyword is the one we have encountered. In this case it is made confusing by the fact that other keywords in the same class are case-insensitive (the I haven't really looked at how other keywords are treated, but at least they have not caused any issues for us so far. Regards, |
Hi @jsundmannorberg, The new 0.1.68 release includes a fix to make the "Host" keyword case-insensitive. Thanks, |
Hi @norrisjeremy, Thanks! Unfortunately it appears that there is a bug in the new version. Now it checks that Regards, |
Hi @jsundmannorberg, Well that is an embarrassing blunder. Would something like this look correct to you?
Thanks, |
Hi @norrisjeremy, That looks like it should work. This kind of bug is surprisingly hard to catch, no worries 😄 Thanks, |
Hi @jsundmannorberg, I believe this issued should now hopefully be fully resolved now in the new 0.1.69 release. Thanks, |
The new version works perfectly. Thanks! |
Hi,
According to
man ssh_config
keywords should be case-insensitive and arguments should be case-sensitive.However, it appears that the "Host" keyword is case-sensitive in the current implementation (on line 127 in
OpenSSHConfig.java
we have a case-sensitive equality checkif(key_value[0].equals("Host")){
)We have seen cases where this leads to confusing bugs when users assume that the config keywords are case-insensitive, so it would probably be good to change the code to match the specification.
Regards,
Johan Sundman Norberg
The text was updated successfully, but these errors were encountered: