Remmina continuously prompts for key unlock password with incorrect username set

Problem Description

When using an SSH connection or SSH tunnel, if an incorrect or empty SSH username is set compared to the user on the host where the SSH public key was sent, SSH authentication will fail and Remmina will continuously prompt for a password, even if the key unlock password is entered correctly.

What is the expected correct behavior?

If this is an issue with SSH, Remmina should at least check for an empty username and throw an error instead of advancing to the continous password prompt. If possible, Remmina should handle the case of an incorrect username or key that may not have been sent to the host. The continuous password prompt is not a proper way to handle this issue as it implies other problems.

Remote System Description

• Server (OS name and version):
• Special notes regarding the remote system (i.e. gateways, tunnel, etc.):

Relevant logs and/or screenshots

Debugging documentation

Please see Remmina debugging

Local System Description

• Client (OS name and version):

• Remmina version ( remmina --version ):

• Installation(s):

  • Distribution package.
  • PPA.
  • Snap.
  • Flatpak.
  • Compiled from sources.
  • Other - detail:

• Desktop environment (GNOME, Unity, KDE, ..):

• Plugin(s):

  • RDP - freerdp version ( xfreerdp --version ):
  • VNC
  • SSH
  • SFTP
  • SPICE
  • WWW
  • EXEC
  • Other (please specify):

• GTK backend (Wayland, Xorg):

• Optional: Include the output of the following commands at the end of this text:

  • remmina --full-version

• sudo lshw -C video

• uname -a

Contributions

In return, or to fix this issue, I'd be willing to:

• Fix this myself.
• Donate ___ and/or have donated ___ towards fixing it.
• Take a donation of ___ to fix it.
• Update the documentation.
• Update the wiki.
• Translate Remmina in my native language(s) (___) on Hosted Weblate.