From 0b38a86c43e597acad2f2e0f9dd3dd8af279b6f7 Mon Sep 17 00:00:00 2001 From: Fulvio Risso Date: Tue, 5 Dec 2023 14:30:51 +0100 Subject: [PATCH] Update crownlabs_ssh.md (#55) --- content/resources/crownlabs_ssh/crownlabs_ssh.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/resources/crownlabs_ssh/crownlabs_ssh.md b/content/resources/crownlabs_ssh/crownlabs_ssh.md index 0a79319..fc9130b 100644 --- a/content/resources/crownlabs_ssh/crownlabs_ssh.md +++ b/content/resources/crownlabs_ssh/crownlabs_ssh.md @@ -22,7 +22,7 @@ This process only needs to be done once per **device.** All CrownLabs VMs are characterized by **private IP addresses**, and cannot be accessed directly through SSH. As shown in the figure below, it is necessary to first establish the SSH connection through a **bastion**, which instead is publicly accessible, and then **jump** to the final destination (i.e., the VM). -This can be achieved with the `ssh -J bastion@crownlabs.polito.it crownlabs@10.1.2.3` command, in which the local **SSH client** first connects to the bastion (indeed, the **-J** option specifies a **ProxyJump**), leveraging the generated **SSH key-pair** for authentication purposes. +This can be achieved with the `ssh -J bastion@ssh.crownlabs.polito.it crownlabs@10.1.2.3` command, in which the local **SSH client** first connects to the bastion (indeed, the **-J** option specifies a **ProxyJump**), leveraging the generated **SSH key-pair** for authentication purposes. Specifically, the **bastion** checks the **client**'s authentication attempt using the **public key** previously uploaded to the **CrownLabs Dashboard**. If authentication succeeds, you are then redirected to your **VM**.