sbrl/Linux-101
1
0
Fork 0
Code Issues 1 Pull requests Releases Wiki Activity

[201/lab sheet] fill in last example password manager
All checks were successful
continuous-integration/laminar-elessar Build 73 succeeded in 1 minute 33 seconds .
Details

Browse source
This commit is contained in:
Starbeamrainbowlabs 2019-10-28 13:18:55 +00:00
parent e86218f944
commit 117ae241f4
Signed by: sbrl
GPG key ID: 1BE5172E637709C2
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
201/Lab-Sheet.md
View file

@ -118,6 +118,8 @@ Now that the user has been created, we should ensure that that user can execute
Execute the command as above, replacing `"yourusername"` with the user you created in the previous step. Execute the command as above, replacing `"yourusername"` with the user you created in the previous step.
This adds your new user account to the `sudo` group of users on the system, which is a group of users permitted to use the `sudo` command to run commands as other users - including `root`.
At this point, you should be able to logout and log back in as the new user account you've just created - you should do this now. At this point, you should be able to logout and log back in as the new user account you've just created - you should do this now.
If you're creating a new account to replace the default non-root user account, it's a good idea at this point to delete the old default user account now. This helps keep your VM secure, as fewer user accounts (note: system accounts are a different topic) mean fewer potential entry points for attackers. If you're creating a new account to replace the default non-root user account, it's a good idea at this point to delete the old default user account now. This helps keep your VM secure, as fewer user accounts (note: system accounts are a different topic) mean fewer potential entry points for attackers.
@ -135,7 +137,7 @@ passwd
It will ask you for your current password, and ten for a new password twice. Once done, try logging out and then back in again to see that your new password has been applied. Note that this will also affect things when you're using `sudo`: you should use your new password instead of the old one, since the password you use with `sudo` is synced with your local user account. It will ask you for your current password, and ten for a new password twice. Once done, try logging out and then back in again to see that your new password has been applied. Note that this will also affect things when you're using `sudo`: you should use your new password instead of the old one, since the password you use with `sudo` is synced with your local user account.
It's also worth mentioning at this point that storing said password in a secure _password manager_ would be a good idea, rather than writing it down in a text file. Password databases are encrypted with a master password, which is much more secure. Many password managers exist, from [KeePass](https://keepass.info/) to [Firefox Lockwise](https://www.mozilla.org/en-GB/firefox/lockwise/) to [(insert another suggestion here)]() It's also worth mentioning at this point that storing said password in a secure _password manager_ would be a good idea, rather than writing it down in a text file. Password databases are encrypted with a master password, which is much more secure. Many password managers exist, from [KeePass](https://keepass.info/) to [Firefox Lockwise](https://www.mozilla.org/en-GB/firefox/lockwise/) to [BitWarden](https://bitwarden.com/), and many more.
### Securing SSH ### Securing SSH