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.
Description of problem:
2. What is the nature and description of the request?
The location of the private-key of the ssh-key used by virt-who to connect to libvirt should be configurable in the virt-who conf file.
3. Why does the customer need this? (List the business requirements here)
For security and compliance reasons is requested to use a dedicated ssh-key for applicative uses respect to the one used for administrative connection.
4. How would the customer like to achieve this? (List the functional requirements here)
With the addition of a new option in virt-who config file
5. For each functional requirement listed in question 4, specify how Red Hat and Customer can test to confirm the requirement is successfully implemented.
This can be tested by generating 2 ssh keys with different names and placing the public one of the dedicated to virt-who key into the hypervisor and verifying that the connection could happen.
6. Is there already an existing RFE upstream or in Red Hat bugzilla?
No
7. How quickly does this need resolved? (desired target release)
As soon as possible, it should be made available both on RHEL6 and RHEL7
8. Does this request meet the RHEL Inclusion criteria (please review)
Yes
9. List the affected packages
virt-who
Version-Release number of selected component (if applicable):
virt-who-0.19-6