-
Notifications
You must be signed in to change notification settings - Fork 171
Spaces In 'identityfile' Path #100
Comments
thanks for the report. checking the user input is w/ quotes or not might be tricky. but it seems we can quote the value of identityFile regardless of the user input. so as long as we do that, it doesn't matter the value has spaces on it or not, right? |
Er, sorry - I don’t follow. Maybe I’m doing something wrong, but if I use either single or double quotes, or backslash escaped spaced on the command line, the string that is inserted into ~/.ssh/config does not have quotes around it - and the spaces are not escaped. Which causes problems. Have I just misunderstood how I add an entry with a space in the identity path? Max Manders On 10 April 2015 at 11:28:26, Emre Yılmaz (notifications@github.com) wrote: thanks for the report. it seems we can quote the value of identityFile. so as long as we do that, it doesn't matter the value has spaces on it or not, right? — |
no, you're not doing anything wrong. it's my english I think :-) it's certainly a bug, storm should quote that value. will be done in a couple days, looks like a quick fix. |
You are my hero :-D Max Manders On 10 April 2015 at 11:32:43, Emre Yılmaz (notifications@github.com) wrote: no, you're not doing anything wrong. it's my english I think :-) it's certainly a bug, storm should quote that value. will be done in a couple days, looks like a quick fix. — |
This is fixed with 0.6.7. |
Depending on how a user chooses to manage their identities, keys might exist in folders that are named with spaces. In this case, no combination of quoting or escaping the spaces while using
storm add
results in a quoted identityfile line in ~/.ssh/config. To get such hosts to work, the line must be manually quoted. Would it be possible to ensure that if ' --id_file' is quoted on the command line, those quotes are persisted through to SSH config?The text was updated successfully, but these errors were encountered: