External Tools Request

[MrDwight]

Request: External Tools

When creating an external tools command, there is an option to "run elevated." I am requesting a feature: to be able to use the saved credentials under Tools | Options | Credentials instead of having to manually enter elevated credentials via Windows UAC when using the External Tools "run elevated" option.

Desired Behavior

When setting up an External Tools command, you would check "run elevated" and then be presented with an option to use the saved credentials previously entered under Tools | Options | Credentials, instead of being presented with a Windows UAC credentials prompt/dialog upon execution of the External Tool command.

## Current Behavior

Currently, when setting up an External Tools command, and checking "run elevated," users are presented with a Windows UAC credentials prompt/dialog when executing the External Tool command.

## Possible Solution

Unknown.

## Steps to Reproduce (for bugs)

1. Create a new external tool.
2. Check the "run elevated" option for that external tool.
3. Execute that external tool.
4. You should be presented with a Windows UAC credentials prompt/dialog.

## Context

Want to find a way to eliminate unnecessary credentials prompts especially when dealing with multiple computers. While it may not be the most secure option, it really should be left to the end user to decide that on their own if they want to run the risk. And user can always lock their Windows desktop to prevent unauthorized access to mRemoteNG.

## Your Environment

• Version used: mRemoteNG ver 1.77.1.27713
• Operating System and version (e.g. Windows 10 1709 x64): Windows 10 22H2 x64.

[Kvarkas]

Good shot! But its a major change what i am working at the moment - we try do not save anything within an app so people cant complain what we don't save it properly and passwords was stolen :) however we allow to encrypt and save is user persist but accept all responsibility on him not on us. With such conditions i think we could add this in featured version (don't get scared of version i labeled, that due plan is to move to new .net library so version changes) after next release I will start migration. And then we could review this suggestion to add into plan.