mRemoteNG / mRemoteNG/mRemoteNG
Feature Request: Allow setting name of connection as value of domain
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
Either create a new setting in the config for a folder or if a period is used for domain, don't use the current hostname that mRemoteNG is running on as the value of the domain setting.
Current Behavior
AFAIK, current configuration doesn't allow for setting the domain of the connection to be the same as the name of the connection
Setting a period as the value of the domain setting will use the name of the current host that mRemoteNG is running on as the value and not the destination host.
Possible Solution
?
Context
Am on a host that's part of the domain but will occasionally need to RDP into hosts off the domain.
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 by tracing how folder configuration and the connection domain setting are represented and how RDP connections resolve a period-valued domain. Confirm the intended behavior with the existing configuration model and authentication flow; done means a connection can use its own name as the domain without substituting the local hostname.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authentication, desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100