Bug 1274104 - [RFE] add --sshkey option to sshpw kickstart command
Summary: [RFE] add --sshkey option to sshpw kickstart command
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1240410
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-21 23:56 UTC by Brian Lane
Modified: 2016-02-24 16:08 UTC (History)
6 users (show)

Fixed In Version: anaconda-24.7-1
Doc Type: Enhancement
Doc Text:
Clone Of: 1240410
Environment:
Last Closed: 2016-02-24 16:08:49 UTC
Type: Bug


Attachments (Terms of Use)

Description Brian Lane 2015-10-21 23:56:41 UTC
+++ This bug was initially created as a clone of Bug #1240410 +++

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:

--- Additional comment from RHEL Product and Program Management on 2015-07-06 13:38:39 PDT ---

Since this bug report was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Brian Lane on 2015-10-21 16:55:44 PDT ---

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.


Note You need to log in before you can comment on or make changes to this bug.