Question about persisting SSH “Algorithm Support” settings in Remote Desktop Manager for macOS 26.1
Hello,
I am using Remote Desktop Manager on macOS and I have a question regarding the SSH “Algorithm Support” settings, specifically related to their persistence.
Environment:
• OS: macOS 26.1
• Remote Desktop Manager: 2025.3.8.3
• Connection type: SSH / Terminal
Issue description:
On the macOS version of Remote Desktop Manager, the only location where I can configure SSH algorithm settings (Cipher, Host Key, KEX, MAC) is:
Remote Desktop Manager (top menu) > Settings > Types > Terminal > Algorithm
There are no per-connection Algorithm Support options available on macOS, and no other settings page allows these algorithms to be defined.
When I modify the Algorithm Support options in this section, the changes work for the current session. However, after quitting Remote Desktop Manager and reopening it, all of these settings revert back to their default values. In other words, the Algorithm Support configuration does not persist between application restarts, and I must manually reconfigure it every time I open RDM.
This makes it difficult to maintain consistent SSH behavior, especially when certain servers require non-default or legacy algorithms.
Expected behavior:
I would expect the Algorithm Support settings configured under Settings > Types > Terminal > Algorithm to be saved permanently, either as global defaults or per-connection overrides.
Questions:
1. Is there a way to make these Algorithm Support settings persistent on macOS so they are not lost after restarting RDM?
2. Are these settings intended to be global defaults, or should they be stored per-connection?
3. Is this behavior a known limitation or a bug in the macOS version of Remote Desktop Manager?
4. If this is a known issue, is there any recommended workaround (file-based configs, templates, etc.) to avoid reconfiguring these settings every time?
Thank you for your assistance.
Best regards,
Willy
Hi,
It looks like a bug. Your settings should persist when you exit the application. I investigated and found the cause, and I’ll fix it, but I can’t give a timeline for when the update will be released.
Best regards,
Jesse Galarneau