Bug 1389800

Summary:	[REBASE] Tigervnc from 1.1 to 1.7
Product:	Red Hat Enterprise Linux 6	Reporter:	Pat Riehecky <riehecky>
Component:	tigervnc	Assignee:	Jan Grulich <jgrulich>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.8	CC:	csieh, desktop-qa-list, jgrulich, mboisver, misterbonnie, tpelka
Target Milestone:	rc	Keywords:	Rebase
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	tigervnc-rebase	Environment:
Last Closed:	2017-12-06 10:40:03 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:

Description Pat Riehecky 2016-10-28 16:55:46 UTC

Description of problem:
Newer versions of TigerVNC have a number of helpful new features.

In particular:
- IPv6 support
- View Only Password
- Fixes to TLS support
- Improved java client
- ~/.vnc/config options support

Version-Release number of selected component (if applicable): tigervnc-1.1


How reproducible:
100%

Steps to Reproduce:
1.seek to use newer features
2.
3.

Actual results:
Newer features not present

Expected results:
features present.

Additional info:

Comment 2 Jan Grulich 2016-11-01 06:28:59 UTC

I guess this is doable (from technical point of view), but I don't think this is going to happen for RHEL 6. You have much higher chance getting it to RHEL 7.

Comment 3 Jan Kurik 2017-12-06 10:40:03 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/