From 95e75b3ac69e3525275155d579694fa546d97a6f Mon Sep 17 00:00:00 2001 From: Sam Foo Date: Tue, 23 Jan 2018 09:22:00 -0500 Subject: [PATCH 1/5] Remove mixed indentation for use public key authentication --- .../use-public-key-authentication-with-ssh.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/security/authentication/use-public-key-authentication-with-ssh.md b/docs/security/authentication/use-public-key-authentication-with-ssh.md index d56a733e194..8dd73b7fcd1 100644 --- a/docs/security/authentication/use-public-key-authentication-with-ssh.md +++ b/docs/security/authentication/use-public-key-authentication-with-ssh.md @@ -47,15 +47,15 @@ If you accidentally lock yourself out of your Linode this way, you can use [Lish ssh-keygen - **Optional:** to increase the security of your key, increase the size with the `-b` flag. The minimum value is 768 bytes and the default, if you do not use the flag, is 2048 bytes. We recommend a 4096 byte key: + **Optional:** to increase the security of your key, increase the size with the `-b` flag. The minimum value is 768 bytes and the default, if you do not use the flag, is 2048 bytes. We recommend a 4096 byte key: - ssh-keygen -b 4096 + ssh-keygen -b 4096 2. Answer all questions when prompted. You can accept the defaults for everything except the passphrase. When you get to the passphrase question, enter a series of letters and numbers for the passphrase twice; once to enter the new passphrase and once to confirm. - **Important:** make a note of your passphrase, as you will need it later. + **Important:** make a note of your passphrase, as you will need it later. - You may accept the defaults for the other questions by pressing *Return* when prompted: + You may accept the defaults for the other questions by pressing *Return* when prompted: user@linode: ssh-keygen -b 4096 Generating public/private rsa key pair. @@ -81,7 +81,7 @@ Please note that the following steps are performed on your remote location/Linod mkdir .ssh - The following steps are performed on your local machine/PC: + The following steps are performed on your local machine/PC: 3. Copy the *public key* into the `~/.ssh/authorized_keys` file on the **remote machine**, using the following command. Substitute your own SSH user and host names: From 4550608a04eb75509828f65fe5a8eb4e0775be36 Mon Sep 17 00:00:00 2001 From: Sam Foo Date: Tue, 23 Jan 2018 11:18:38 -0500 Subject: [PATCH 2/5] Fixed indentation for accounts and passwords --- docs/platform/accounts-and-passwords.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/platform/accounts-and-passwords.md b/docs/platform/accounts-and-passwords.md index 046a4e3803e..76ab7f39e04 100644 --- a/docs/platform/accounts-and-passwords.md +++ b/docs/platform/accounts-and-passwords.md @@ -58,11 +58,11 @@ Here's how to set a user's access permissions: 3. Enter your password and click **Authenticate**. The *User Manager* webpage appears. 4. Locate the user in the list and select the **Edit Permissions** link. The webpage shown below appears. -[![Configure permissions for a user in the Linode Manager.](/docs/assets/922-user1-small.png)](/docs/assets/921-user1.png) + [![Configure permissions for a user in the Linode Manager.](/docs/assets/922-user1-small.png)](/docs/assets/921-user1.png) 5. Select checkboxes in the **Global Grants** section to allow the user to add Linodes, Domains, and NodeBalancers to the account, create StackScripts, access all billing information, and cancel the entire account. - {{< note >}} + {{< note >}} Granting access to settings denoted with a dollar sign (\$) will allow the user perform actions that incur billing costs, such as adding or resizing a Linode. {{< /note >}} From a6858fa22582526a52013c79163d640e40fca44b Mon Sep 17 00:00:00 2001 From: Sam Foo Date: Tue, 23 Jan 2018 11:21:47 -0500 Subject: [PATCH 3/5] Fixed escaped chars in fail2ban --- docs/security/using-fail2ban-for-security.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/security/using-fail2ban-for-security.md b/docs/security/using-fail2ban-for-security.md index 13c4fcf0e94..23283f4a953 100644 --- a/docs/security/using-fail2ban-for-security.md +++ b/docs/security/using-fail2ban-for-security.md @@ -58,7 +58,7 @@ Follow the [Getting Started](/docs/getting-started) guide to configure your basi {{< note >}} Should you encounter the error that there is "*no directory /var/run/fail2ban to contain the socket file /var/run/fail2ban/fail2ban.sock*", create the directory manually: -'mkdir /var/run/fail2ban' + mkdir /var/run/fail2ban {{< /note >}} ### Debian @@ -79,9 +79,10 @@ Should you encounter the error that there is "*no directory /var/run/fail2ban to {{< note >}} The current version of Sendmail in Debian Jessie has an [upstream bug](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293017) which causes the following errors when installing `sendmail-bin`. The installation will hang for a minute, but then complete. -Creating /etc/mail/sendmail.cf... -ERROR: FEATURE() should be before MAILER() MAILER(`local') must appear after FEATURE(`always_add_domain') -ERROR: FEATURE() should be before MAILER() MAILER(`local') must appear after FEATURE(`allmasquerade') + + Creating /etc/mail/sendmail.cf... + ERROR: FEATURE() should be before MAILER() MAILER('local') must appear after FEATURE('always_add_domain') + ERROR: FEATURE() should be before MAILER() MAILER('local') must appear after FEATURE('allmasquerade') {{< /note >}} ### Fedora From 2474c0577692eca97d629760d7152d85034c274d Mon Sep 17 00:00:00 2001 From: Jared Kobos Date: Wed, 24 Jan 2018 11:29:22 -0500 Subject: [PATCH 4/5] Image and spacing fixes --- docs/platform/accounts-and-passwords.md | 2 +- .../use-public-key-authentication-with-ssh.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/platform/accounts-and-passwords.md b/docs/platform/accounts-and-passwords.md index 76ab7f39e04..c9928cbef43 100644 --- a/docs/platform/accounts-and-passwords.md +++ b/docs/platform/accounts-and-passwords.md @@ -63,7 +63,7 @@ Here's how to set a user's access permissions: 5. Select checkboxes in the **Global Grants** section to allow the user to add Linodes, Domains, and NodeBalancers to the account, create StackScripts, access all billing information, and cancel the entire account. {{< note >}} -Granting access to settings denoted with a dollar sign (\$) will allow the user perform actions that incur billing costs, such as adding or resizing a Linode. +Granting access to settings denoted with a dollar sign ($) will allow the user perform actions that incur billing costs, such as adding or resizing a Linode. {{< /note >}} 6. Select checkboxes in the other sections to allow the user to access certain features and sections of the Linode Manager. diff --git a/docs/security/authentication/use-public-key-authentication-with-ssh.md b/docs/security/authentication/use-public-key-authentication-with-ssh.md index 8dd73b7fcd1..68b68576c3f 100644 --- a/docs/security/authentication/use-public-key-authentication-with-ssh.md +++ b/docs/security/authentication/use-public-key-authentication-with-ssh.md @@ -135,7 +135,7 @@ When PuTTYgen has finished downloading, it can be run immediately, without insta 6. Before you continue, you will need to copy the newly-created public key to Notepad. Just select the text and copy it to a new text file. Be sure the file is saved in a location you remember, as you will need it later. - ![Copy the public key to a text file.](/docs/assets/1476-key-txt-file.png) + ![Copy the public key to a text file](/docs/assets/1476-key-txt-file.png) {{< caution >}} When saving the public key, make sure you save it in a plaintext format such as .txt. Other file formats such as .rtf and .doc may add extra characters to the key through encoding, which may prevent your keypair from matching. The public key should be a single line, with no breaks. @@ -143,11 +143,11 @@ When saving the public key, make sure you save it in a plaintext format such as 7. Enter a passphrase in the **Key passphrase** text field, and enter it again to confirm. The passphrase can be any string of letters and numbers. The passphrase should be something unique and not easily recognized. **Important:** make a note of your passphrase, as you will need it later. - ![Enter a new passphrase.](/docs/assets/1465-new-passphrase.png) + ![Enter a new passphrase](docs/assets/1465-new-passphrase.png) 8. After you have entered your passphrase, click on the **Save private key** button. This will save the private key to your PC. - ![Click on the Save private key button.](/docs/assets/1472-private-key-button.png) + ![Click on the Save private key button](/docs/assets/1472-private-key-button.png) 9. Keep the default location and name of the private key file and click on the **Save** button. Note that if you plan on creating multiple keys to connect to different SSH servers, you will need to save each pair of keys for each server with different names to prevent overwriting the key files. Make a note of the name and location of the private key. You'll need it in the next section. From f64cd3e6284b2911b08b6076b3a3529b9831b7ad Mon Sep 17 00:00:00 2001 From: Sam Foo Date: Wed, 24 Jan 2018 11:33:25 -0500 Subject: [PATCH 5/5] Capitalized PNG to png --- ...463-begin-install.PNG => 1463-begin-install.png} | Bin ...{1464-generate-key.PNG => 1464-generate-key.png} | Bin ...5-new-passphrase.PNG => 1465-new-passphrase.png} | Bin ...6-new-public-key.PNG => 1466-new-public-key.png} | Bin docs/assets/{1468-warning.PNG => 1468-warning.png} | Bin ...om-generating.PNG => 1470-random-generating.png} | Bin ...ation.PNG => 1473-private-key-file-location.png} | Bin ...ve-private-key.PNG => 1474-save-private-key.png} | Bin ...475-saved-session.PNG => 1475-saved-session.png} | Bin 9 files changed, 0 insertions(+), 0 deletions(-) rename docs/assets/{1463-begin-install.PNG => 1463-begin-install.png} (100%) rename docs/assets/{1464-generate-key.PNG => 1464-generate-key.png} (100%) rename docs/assets/{1465-new-passphrase.PNG => 1465-new-passphrase.png} (100%) rename docs/assets/{1466-new-public-key.PNG => 1466-new-public-key.png} (100%) rename docs/assets/{1468-warning.PNG => 1468-warning.png} (100%) rename docs/assets/{1470-random-generating.PNG => 1470-random-generating.png} (100%) rename docs/assets/{1473-private-key-file-location.PNG => 1473-private-key-file-location.png} (100%) rename docs/assets/{1474-save-private-key.PNG => 1474-save-private-key.png} (100%) rename docs/assets/{1475-saved-session.PNG => 1475-saved-session.png} (100%) diff --git a/docs/assets/1463-begin-install.PNG b/docs/assets/1463-begin-install.png similarity index 100% rename from docs/assets/1463-begin-install.PNG rename to docs/assets/1463-begin-install.png diff --git a/docs/assets/1464-generate-key.PNG b/docs/assets/1464-generate-key.png similarity index 100% rename from docs/assets/1464-generate-key.PNG rename to docs/assets/1464-generate-key.png diff --git a/docs/assets/1465-new-passphrase.PNG b/docs/assets/1465-new-passphrase.png similarity index 100% rename from docs/assets/1465-new-passphrase.PNG rename to docs/assets/1465-new-passphrase.png diff --git a/docs/assets/1466-new-public-key.PNG b/docs/assets/1466-new-public-key.png similarity index 100% rename from docs/assets/1466-new-public-key.PNG rename to docs/assets/1466-new-public-key.png diff --git a/docs/assets/1468-warning.PNG b/docs/assets/1468-warning.png similarity index 100% rename from docs/assets/1468-warning.PNG rename to docs/assets/1468-warning.png diff --git a/docs/assets/1470-random-generating.PNG b/docs/assets/1470-random-generating.png similarity index 100% rename from docs/assets/1470-random-generating.PNG rename to docs/assets/1470-random-generating.png diff --git a/docs/assets/1473-private-key-file-location.PNG b/docs/assets/1473-private-key-file-location.png similarity index 100% rename from docs/assets/1473-private-key-file-location.PNG rename to docs/assets/1473-private-key-file-location.png diff --git a/docs/assets/1474-save-private-key.PNG b/docs/assets/1474-save-private-key.png similarity index 100% rename from docs/assets/1474-save-private-key.PNG rename to docs/assets/1474-save-private-key.png diff --git a/docs/assets/1475-saved-session.PNG b/docs/assets/1475-saved-session.png similarity index 100% rename from docs/assets/1475-saved-session.PNG rename to docs/assets/1475-saved-session.png