Invalid RDP credentials report connection error

Bug #941649 reported by Sami Haahtinen
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
remmina (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Attempting to connect to an RDP server with invalid credentials report connection error after accepting the SSL certificate.

remmina reports the following in the console:

A valid certificate for the wrong name should NOT be trusted!
SSL_read: Failure in SSL library (protocol error?)
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.

GUI doesn't reflect this. Instead the GUI reports an connection error.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: remmina 1.0.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Mon Feb 27 00:11:41 2012
SourcePackage: remmina
UpgradeStatus: Upgraded to precise on 2011-12-27 (61 days ago)

Revision history for this message
Sami Haahtinen (ressu) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in remmina (Ubuntu):
status: New → Confirmed
Revision history for this message
hepsoe (hepsoe) wrote :

I've been struggling to get past this point as well.
The only connection method working for me now is VNC.

Is something being done to resolve this issue?

Revision history for this message
Sami Haahtinen (ressu) wrote : Re: [Bug 941649] Re: Invalid RDP credentials report connection error

There is a workaround.

You can either remove the offending line from ~/.freerdp/known_hosts or
remove the whole file.

Revision history for this message
Yan Liu (yanliu) wrote :

Removing ~/.freerdp/knwon_hosts does not work for me. All my conn use NLA for auth.

But I found a way out:
- clear domain name or password in connection setting
- save and connect; input password and domain name again; then conn works well
- disconnect; and re-input password and domain name; then save

It seems after upgrade, remmina could not load password correctly from previous connection config file; but without clearing out, it doesn't write to config either.

I also found that some of cert footprint were written to .freerdp/known_hosts, some not. Very strange.

Revision history for this message
David Clayton (dcstar) wrote :

Yan Liu's workaround fixed it for me - quite annoying after upgrading from Ubuntu 10.04 to 12.04 and having this problem.

Revision history for this message
Mossroy (mossroy) wrote :
Revision history for this message
Kevin Krumwiede (kjkrum) wrote :

The comments on this issue seem to be off track. This report is not about the fact that some of the protocols don't work, although that may also be an issue. It's about the fact that the error messages in the UI misleadingly indicate a connection problem when there's actually an authentication problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.