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:
Right now, when using libreport-plugin-reportuploader with password-less scp uploads, it takes the private SSH key from /root/.ssh/id_rsa.  We would like to see this option/location configurable.


Version-Release number of selected component (if applicable):
libreport-2.0.9-24.el6.x86_64


How reproducible:
N/A


Steps to Reproduce:
N/A


Actual results:
N/A


Expected results:
N/A

Additional info:
N/A

I think we need something like this:

  curl_easy_setopt(curlUp, CURLOPT_SSH_PUBLIC_KEYFILE, getenv($pub_key));
  curl_easy_setopt(curlUp, CURLOPT_SSH_PRIVATE_KEYFILE, getenv($priv_key));

Upstream commits add the feature:
https://github.com/abrt/libreport/commit/1b521cc87fd05f5c9acf2fcdadb17f6f67d2beb2
https://github.com/abrt/libreport/commit/dd039190c2d51ca499f235ce7b787f17aa096d80
https://github.com/abrt/libreport/commit/19035e980d17a98709c3ee99ab577a2e5e5c1ddf
https://github.com/abrt/libreport/commit/ab7d2a17c6670ea8818ba1740796878cbd05e454
https://github.com/abrt/libreport/commit/35180a97cf7172d733946e605ef2c3432fbab953

Related test:
https://github.com/abrt/abrt/commit/4b308bb30c7d9fddeecd861da95da69da6e45b38

Patches were pushed to rhel-6.8-staging branch.

ABRT test case: https://github.com/abrt/abrt/commit/56ca324a8dabacda9a866a39121d48a662517150

Created attachment 1103502 [details]
add possibility to configure SSH keys

Created attachment 1103503 [details]
uploader: add possibility to set SSH keyfiles

Created attachment 1103504 [details]
spec: add uploader config files and related man page

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0920.html