Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:

Customer want to increase the security level. Right now satellite is using one (non password protected) ssh key to run remote jobs on all of our hosts. They would like to use password protected ssh key, so even after it is somehow extracted from the satellite, the person would have to know the password to use it.


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


Actual results:
existing SSH key do not have passwords to access them

Expected results:
Password protected SSH key for security reasons. 

Additional info:

Well, they can do this themselves. They either can replace the key with their own or just add an passphrase to an already existing key.

Is it a future feature though? It is possible manually right now. Yes, we could document it and we could possibly make the installer generate passphrase protected keys, but almost surely not by default.

Sure Adam. I have suggested a way to achieve it to the customer. Please share if you have a document currently or where we can incorporate this?

I don't really have anything. It could either end up being a KCS or go into the proper docs

That should become a new section in https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/managing_hosts/configuring_and_setting_up_remote_jobs_managing-hosts#doc-wrapper

Hello!
Created PR to add the new section into our guides:
https://github.com/theforeman/foreman-documentation/pull/2817

New section has been added to the documentation:
6.14: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/managing_hosts/configuring_and_setting_up_remote_jobs_managing-hosts#adding-a-passphrase-to-ssh-key-used-for-remote-execution_managing-hosts
6.13: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/managing_hosts/configuring_and_setting_up_remote_jobs_managing-hosts#adding-a-passphrase-to-ssh-key-used-for-remote-execution_managing-hosts
6.12: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/managing_hosts/configuring_and_setting_up_remote_jobs_managing-hosts#adding-a-passphrase-to-ssh-key-used-for-remote-execution_managing-hosts