Commit c84baf7d authored by Peter Arts's avatar Peter Arts Committed by Vitor Meireles De Sousa
Browse files

Add SSH key security disclaimers and 1Password recommendations

parent 8c704206
Loading
Loading
Loading
Loading
+10 −0
Original line number Diff line number Diff line
@@ -32,6 +32,14 @@ Please take time to understand any code that you are asked to copy and paste in

> GitLab uses the SSH protocol to securely communicate with Git. When you use SSH keys to authenticate to the GitLab remote server, you don't need to supply your username and password each time. You can learn more in the [documentation](https://docs.gitlab.com/ee/user/ssh.html).

### Security Recommendation: Use 1Password for SSH Key Generation

We recommend generating and storing your SSH key using 1Password instead of storing it on disk. This approach provides better protection for your private keys. Follow the [1Password SSH key generation guide](https://docs.gitlab.com/user/ssh_advanced/#generate-an-ssh-key-pair-with-1password) for detailed instructions.

### Alternative: Generate SSH Key Locally

If you prefer to generate your SSH key locally, follow these steps:

1. We will use OpenSSH client, which comes pre-installed on GNU/Linux, macOS, and Windows 10. To check your current version run the following command in your terminal or Powershell:

   ```bash
@@ -52,6 +60,8 @@ Please take time to understand any code that you are asked to copy and paste in

   > To keep the steps simple, we are opting to not set a password for the key file. Blank passphrases are not generally considered best practices. You can set a passphrase if desired.

> **Security Warning:** Storing SSH keys on disk poses security risks. Private keys should be protected and never shared. Consider using 1Password or similar secure key management solutions for production environments.

## Task C. Add an SSH key to your GitLab profile

1. Open your browser to the project that you created in Lab 1.
+9 −1
Original line number Diff line number Diff line
@@ -21,7 +21,15 @@ In this lab, you'll learn systematic troubleshooting techniques for CI/CD pipeli

## Task A. Setup the SSH Connection

As a part of this course, you were provided with an SSH key to use for deployments. You will need to add this SSH key to GitLab to use it during your CI/CD process. To do this:
As a part of this course, you were provided with an SSH key to use for deployments. You will need to add this SSH key to GitLab to use it during your CI/CD process.

### Security Recommendation: Use 1Password for SSH Key Management

We strongly recommend using 1Password or similar secure key management solutions to generate and store SSH keys instead of storing them on disk. This provides better protection for your private keys. Follow the [1Password SSH key generation guide](https://docs.gitlab.com/user/ssh_advanced/#generate-an-ssh-key-pair-with-1password) for detailed instructions.

> **Security Warning:** Storing SSH keys on disk poses security risks. Private keys should be protected and never shared. Use secure key management practices.

To add your SSH key to GitLab, follow these steps:

1. Navigate to your project in GitLab.