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:

Currently the only way for customer to select and deselect tls_ciphers is via an unsupported wrapper. We need a way to allow customer to config which ciphers they want and do not want.

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

RHEL 7.6


Actual results:

Currently customers needing this ability due to security protocols can only accomplish this by used an unsupport qemu-kvm wrapper.

Expected results:

We should have a supported method that allows customer to select and deselect which tls_ciphers they want to use.

Additional info:

Multiple customers have requested this ability.

SPICE already provides the required API for that, and it's exposed in QEMU through -spice tls-ciphers=xxx

(In reply to Christophe Fergeau from comment #3)
> SPICE already provides the required API for that, and it's exposed in QEMU
> through -spice tls-ciphers=xxx

Should Frank open a bug in libvirt to set tls-ciphers instead?

(In reply to Douglas Schilling Landgraf from comment #4)
> (In reply to Christophe Fergeau from comment #3)
> > SPICE already provides the required API for that, and it's exposed in QEMU
> > through -spice tls-ciphers=xxx
> 
> Should Frank open a bug in libvirt to set tls-ciphers instead?

BZ#1562032 answer this question.