Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
- vinagre does not accept extra long passwords.
Version-Release number of selected component (if applicable):
- all versions
How reproducible:
- 100%
Steps to Reproduce:
1. Run Vinagre
2. attempt to establish an RDP connection using a password greater than 20 characters
3.
Actual results:
- cannot use passwords greater than 20 characters
Expected results:
- valid passwords are accepted regardless of length
Additional info:
From source:
static gboolean
frdp_authenticate (freerdp *instance,
char **username,
char **password,
char **domain)
{
VinagreTab *tab = VINAGRE_TAB (((frdpContext *) instance->context)->rdp_tab);
VinagreRdpTab *rdp_tab = VINAGRE_RDP_TAB (tab);
VinagreRdpTabPrivate *priv = rdp_tab->priv;
VinagreConnection *conn = vinagre_tab_get_conn (tab);
GtkWindow *window = GTK_WINDOW (vinagre_tab_get_window (tab));
gboolean save_in_keyring = FALSE;
gchar *keyring_domain = NULL;
gchar *keyring_username = NULL;
gchar *keyring_password = NULL;
....
if (vinagre_utils_request_credential (window,
"RDP",
vinagre_connection_get_host (conn),
vinagre_connection_get_domain (conn),
vinagre_connection_get_username (conn),
TRUE,
TRUE,
TRUE,
===> 20, 0 // hardcoded to 20 chars
domain,
username,
password,
&save_in_keyring))
----------------
invoking freerdp directly does not exhibit the password length limitation, so this is merely an arbitrary hardcoded limit of 20 characters, and I am not aware of any password limit on RDP outside of the MS Windows maximums, which for Windows 10 are as follows:
Windows represents passwords in 256-character UNICODE strings. The logon dialog is limited to 127 characters, however.
Source:
http://www.thewindowsclub.com/maximum-length-of-password-windows-10
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:2157
Description of problem: - vinagre does not accept extra long passwords. Version-Release number of selected component (if applicable): - all versions How reproducible: - 100% Steps to Reproduce: 1. Run Vinagre 2. attempt to establish an RDP connection using a password greater than 20 characters 3. Actual results: - cannot use passwords greater than 20 characters Expected results: - valid passwords are accepted regardless of length Additional info: From source: static gboolean frdp_authenticate (freerdp *instance, char **username, char **password, char **domain) { VinagreTab *tab = VINAGRE_TAB (((frdpContext *) instance->context)->rdp_tab); VinagreRdpTab *rdp_tab = VINAGRE_RDP_TAB (tab); VinagreRdpTabPrivate *priv = rdp_tab->priv; VinagreConnection *conn = vinagre_tab_get_conn (tab); GtkWindow *window = GTK_WINDOW (vinagre_tab_get_window (tab)); gboolean save_in_keyring = FALSE; gchar *keyring_domain = NULL; gchar *keyring_username = NULL; gchar *keyring_password = NULL; .... if (vinagre_utils_request_credential (window, "RDP", vinagre_connection_get_host (conn), vinagre_connection_get_domain (conn), vinagre_connection_get_username (conn), TRUE, TRUE, TRUE, ===> 20, 0 // hardcoded to 20 chars domain, username, password, &save_in_keyring)) ---------------- invoking freerdp directly does not exhibit the password length limitation, so this is merely an arbitrary hardcoded limit of 20 characters, and I am not aware of any password limit on RDP outside of the MS Windows maximums, which for Windows 10 are as follows: Windows represents passwords in 256-character UNICODE strings. The logon dialog is limited to 127 characters, however. Source: http://www.thewindowsclub.com/maximum-length-of-password-windows-10