mRemoteNG / mRemoteNG/mRemoteNG
Files transferred by SSH in Tools > SSH File Transfer get added quote marks on remote
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 11.1k
- Forks
- 1.6k
- Avg merge
- 16h 58m
- Merged PRs (30d)
- 55
Description
Expected Behavior
If I transfer a file called foo.bar, and specify the remote filename as foo.bar I expect it to be transferred and named foo.bar but so far every file I've transferred has become named "foo.bar" (with the quotes)
Current Behavior
File is renamed with enclosing quotes - it shouldn't be unless specified in transfer.
Possible Solution
Steps to Reproduce (for bugs)
- Enter hostname, username, password, select file to transfer, name it on the remote system
- Start transfer
- Look on remote system and it will be present but named with enclosing quotes
Context
Just trying to send a file via SCP to a host
Your Environment
Win 10 2004 (have tried on 1909, 1903)
mRemoteNG 1.77.1.2764
Transferring to Cisco IOS XE switch, Ubuntu 20.04, Centos 8.2 - all give the same.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Tools > SSH File Transfer and reproduce the transfer against one of the listed environments, such as Ubuntu or Cisco IOS XE. Trace the SSH/SCP transfer path to identify where the remote filename gains enclosing quotes; done means a transferred foo.bar is stored remotely as foo.bar without quotes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100