Skip to content

Commit 265f7ec

Browse files
committed
BZ2007783 - Updating ssh key in installer
1 parent 1f42275 commit 265f7ec

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

modules/ssh-agent-using.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ endif::openshift-origin[]
166166
----
167167
$ ssh-keygen -t ed25519 -N '' -f <path>/<file_name> <1>
168168
----
169-
<1> Specify the path and file name, such as `~/.ssh/id_rsa`, of the new SSH key. If you have an existing key pair, ensure your public key is in the your `~/.ssh` directory.
169+
<1> Specify the path and file name, such as `~/.ssh/id_ed25519`, of the new SSH key. If you have an existing key pair, ensure your public key is in the your `~/.ssh` directory.
170170
+
171171
[NOTE]
172172
====
@@ -180,11 +180,11 @@ If you plan to install an {product-title} cluster that uses FIPS Validated / Mod
180180
$ cat <path>/<file_name>.pub
181181
----
182182
+
183-
For example, run the following to view the `~/.ssh/id_rsa.pub` public key:
183+
For example, run the following to view the `~/.ssh/id_ed25519.pub` public key:
184184
+
185185
[source,termanal]
186186
----
187-
$ cat ~/.ssh/id_rsa.pub
187+
$ cat ~/.ssh/id_ed25519.pub
188188
----
189189

190190
. Add the SSH private key identity to the SSH agent for your local user, if it has not already been added. SSH agent management of the key is required for password-less SSH authentication onto your cluster nodes, or if you want to use the `./openshift-install gather` command.
@@ -218,7 +218,7 @@ If your cluster is in FIPS mode, only use FIPS-compliant algorithms to generate
218218
----
219219
$ ssh-add <path>/<file_name> <1>
220220
----
221-
<1> Specify the path and file name for your SSH private key, such as `~/.ssh/id_rsa`
221+
<1> Specify the path and file name for your SSH private key, such as `~/.ssh/id_ed25519`
222222
+
223223
.Example output
224224
[source,terminal]

0 commit comments

Comments
 (0)