mRemoteNG / mRemoteNG/mRemoteNG

SQL Connections: Don't ask for custom password after every change is done.

Open
#1,646 2 comments 0 reactions 1 assignee View on GitHub

@Kvarkas is already working on this.

Since Feb 24, 2026.

DBs Need 2 check Security
Dominant language
C#
Stars
11.1k
Forks
1.6k
Avg merge
16h 58m
Merged PRs (30d)
55

Description

Expected Behavior

Only ask for custom encryption password for connections at startup time.

Current Behavior

When using SQL Server connections (tested on MySQL), after every change password is asked in a new popup window. This is quite annoying.

But what is more annoying is that if from another session someone doesn't enter the custom password (pop-up password window loose the focus) and make any change, previous change are lost.

Possible Solution

Store custom encryption password in memory and use it when instance detect some DB connections change.

Steps to Reproduce (for bugs)

  1. Open to instances connected to same database.
  2. Set custom encryption password for connections
  3. Add new connection or modify existing connection

Context

Your Environment

  • Version used: 1.77.0.41307 Portable Edition
  • Windows 10 1909 x64

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.