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 1751073 - RFE: ability to provide per-connection TLS certs to VNC connections
Summary: RFE: ability to provide per-connection TLS certs to VNC connections
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-viewer
Version: ---
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1785222
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-11 06:43 UTC by mxie@redhat.com
Modified: 2021-11-18 13:48 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1751065
Environment:
Last Closed: 2021-03-11 07:31:01 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 chhu 2019-11-22 05:59:07 UTC 
Test on cnv2.1(with RHEL-AV8.0.1) hit same issue.

1. Create VMI on cnv2.1 with win10 OS
2. Try to connect to the VMI by virtctl vnc, the console disappeared immediately, hit error below:
---------------------------------------------------------------------------------------------
{"component":"virtctl","level":"info","msg":"remote-viewer connected in 86.348494ms","pos":"vnc.go:148","timestamp":"2019-11-22T13:02:50.486719Z"}
Error encountered: read tcp 127.0.0.1:40030->127.0.0.1:39148: read: connection reset by peer )
----------------------------------------------------------------------------------------------
3. Try more times, 1 time connected to the VMI, login to the win10 and touch file in it, the win10 OS is OK.
Comment 2 chhu 2019-11-22 07:39:03 UTC 
(In reply to chhu from comment #1)
> Test on cnv2.1(with RHEL-AV8.0.1) hit same issue.
> 
> 1. Create VMI on cnv2.1 with win10 OS
> 2. Try to connect to the VMI by virtctl vnc, the console disappeared
> immediately, hit error below:
> -----------------------------------------------------------------------------
> ----------------
> {"component":"virtctl","level":"info","msg":"remote-viewer connected in
> 86.348494ms","pos":"vnc.go:148","timestamp":"2019-11-22T13:02:50.486719Z"}
> Error encountered: read tcp 127.0.0.1:40030->127.0.0.1:39148: read:
> connection reset by peer )
> -----------------------------------------------------------------------------
> -----------------
> 3. Try more times, 1 time connected to the VMI, login to the win10 and touch
> file in it, the win10 OS is OK.

Changed the nic from rtl8139 to e1000,virtio; virtctl vnc VMI* can succeed with higher ratio.
Comment 3 Daniel Berrangé 2019-12-19 12:21:45 UTC 
In the original bug this was cloned from which involved RHEV, we confirmed that this is due to not having the CA cert installed. GTK-VNC expects the cert on disk, and so there's no way for virt-viewer to privide it from the console.vv file.

Can you either confirm that the CNV tests also involved TLS for VNC, or provide the output of virt-viewer when using the '--gtk-vnc-debug' to connect to CNV.
Comment 10 RHEL Program Management 2021-03-11 07:31:01 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.
Note You need to log in before you can comment on or make changes to this bug.