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:
When using the inst.sshd option and a kickstart installation, using authorized keys would be appreciated.  the sshpw functionality is already there.

Version-Release number of selected component (if applicable): rhel 7.1 release media


How reproducible: Always


Steps to Reproduce:
1. start installation with inst.sshd boot command and sshkey kickstart option
2.
3.

Actual results:
Unknown command: sshkey

Expected results:
Able to authenticate using pubkey to the installing system

Additional info:

sshkey is for setting the sshkeys of users on the installed system, not during installation.

We could probably add a --sshkey argument to the sshpw command, but this will have to happen in upstream Fedora Anaconda first.

Now in upstream Anaconda and pykickstart. bug 1274104

Verified on anaconda-21.48.22.80-1. I was able to login to running installation ussing ssh key when "sshpw --username=root --sshkey '$PUBLIC_KEY'" was in kickstart.

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/RHEA-2016-2158.html