Skip to content
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

Jump to bottom

Path to private key not quoted in Open in Terminal #8745

Closed
cyberduck opened this issue Apr 14, 2015 · 1 comment
Closed

Path to private key not quoted in Open in Terminal #8745

cyberduck opened this issue Apr 14, 2015 · 1 comment
Assignees
@dkocher
Labels
bug fixed sftp SFTP Protocol Implementation
Milestone
4.7

Comments

@cyberduck
Copy link
Collaborator

7cf6c8b created the issue

During menu Go -> Open In Terminal.app, if your key file store in a path that has space (example inside a folder called "My Keys"), the operation will failed.

Suggest to include double quotes for the location of the key file.

Example:

ssh -t -i /Users/myname/My Keys/Project/Security/Keys/myname.pem root@104.236.68.123 -p 22 "cd \/root && exec \$SHELL"
Warning: Identity file /Users/myname/My not accessible: No such file or directory.
ssh: Could not resolve hostname Keys/Project/Security/Keys/myname.pem: nodename nor servname provided, or not known
@cyberduck
Copy link
Collaborator Author

@dkocher commented

In d7fdf26.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug fixed sftp SFTP Protocol Implementation
Projects
None yet
Milestone
4.7
Development

No branches or pull requests
2 participants
@dkocher @cyberduck