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.

Bug 1290449

Summary: [RFE] Improve error messages passed up from freerdp
Product: Red Hat Enterprise Linux 8 Reporter: Joe Wright <jwright>
Component: vinagreAssignee: David King <dking>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.3CC: dking, mkasik, tpopela
Target Milestone: rcKeywords: FutureFeature
Target Release: 8.3Flags: pm-rhel: mirror+
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-01 03:02:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1291254    
Bug Blocks: 1420851    

Description Joe Wright 2015-12-10 14:37:31 UTC
What is the nature and description of the request?  
- vinagre reports connection issues as 'connection error' instead of the more verbose issue reported by the application relied upon (in this example, xfreerdp)
  
Why does the customer need this? (List the business requirements here)  
- diagnosing issues such as duplicate keys or invalid host keys has unnecessary added difficulty
  
How would the customer like to achieve this? 
- pass the error up from the underlying application instead of using generic error messages
  
For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
- Error reported by underlying application is reported by vinagre

Is there already an existing RFE upstream or in Red Hat Bugzilla?  
- no
  
Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
- as soon as possible
  
List any affected packages or components.  
- vinagre
- xfreerdp

Comment 2 Marek Kašík 2015-12-14 12:43:45 UTC
We need newer FreeRDP for this (1.1 at least). There is (*pVerifyChangedCertificate) callback defined in it which allows us to inform user about change of fingerprint of certificate of remote machine so that he can accept or reject the new certificate.
I've filed a rebase request for FreeRDP here: https://bugzilla.redhat.com/show_bug.cgi?id=1291254.

Comment 4 Marek Kašík 2017-08-08 13:22:44 UTC
I'm moving this for consideration for 7.6 since the FreeRDP won't be rebased in 7.5.

Comment 10 RHEL Program Management 2020-11-01 03:02:51 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.