LFS211 Lab 5.3

Hi. I have a question related to practice. Should I log in to my root account with su to append using cat to /root/.ssh/authorized_keys?
It's still asking for the password after I try to ssh.
Maybe I did something wrong that I am not aware of.
Comments
-
I fixed this by restoring the permissions of the file /root/.ssh/authorized_keys to the other user than root. Is this ok?
0 -
Hi, you are referring to this step, correct? For security purposes, I would not change the owner of the files under /etc to a regular owner.
cat /home/student/.ssh/authorized_keys >> /root/.ssh/authorized_keys
In the Labs, you might see the '#' prompt used as opposed to '$'. The '#' prompt implies that this step needs to be performed as "root". You can login as "root," but this is highly discouraged, especially on production systems! Why? The main reason is that there is no accountability. If you are the only person who has the "root" password on that system, then it might be more acceptable. Otherwise, if several people have the "root" password, we don't know who is logged in as "root"; it could be a number of people, including someone who happened to break into your system! So, I recommend that you don't login as "root" on any production system. Your own desktop or Lab system, where you are the only user on that system, is acceptable, but not on a general purpose production system (except for single-user mode, of course). You can use the "su" command to get a "root" sub-shell. I recommend that you use "su -" since the lone hyphen will simulate a login, thus executing other dot-files as if the user that you switched to (in this case, "root") had logged in. You can also use the "sudo" command. On Distros like Ubuntu, you have to use "sudo" because the "root" user does not have a valid password! You can use "sudo -i" to give yourself an interactive "root" shell, similar to how "su" works, but without giving the "root" password. If you do want to use the "sudo" command, which is the safest and best accountable method to temporarily gain elevated privileged, there is a trick you have to do in order to do I/O redirection. If you just type, "sudo cat /home/student/.ssh/authorized_keys >> /root/.ssh/authorized_keys" it will not work correctly. Why? Because the shell you are in as a non-root user first sets-up the I/O redirection as the non-privileged user, and then executes the "sudo" command giving you alternate (in this case, "root") privilege. In order to do commands that include I/O redirection (as "root"), you need to do something like this:
$ sudo bash -c 'cat /home/student/.ssh/authorized_keys >> /root/.ssh/authorized_keys'
What happens is that the "sudo" command is executing a "bash" sub-shell as "root" that then using the command after the "-c" that I put into quotes, that then executes the entire command, including the I/O redirection. This is what I call the "bash -c" trick. Note, it is only needed for I/O redirection. The following command in the Lab could be simply done as:
$ sudo chown root.root /root/.ssh/authorized_keys $ sudo chmod 640 /root/.ssh/authorized_keys
As a Sys Admin, you will use the "bash -c" trick often. Good luck.
1 -
Thank you! I feel really honoured by this answer.
0
Categories
- 8.8K All Categories
- 12 LFX Mentorship
- 65 LFX Mentorship: Linux Kernel
- 355 Linux Foundation Boot Camps
- 226 Cloud Engineer Boot Camp
- 68 Advanced Cloud Engineer Boot Camp
- 23 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 719 Training Courses
- 14 LFC110 Class Forum
- 16 LFD102 Class Forum
- 94 LFD103 Class Forum
- 2 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 14 LFD254 Class Forum
- 419 LFD259 Class Forum
- 78 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 15 LFS200 Class Forum
- 683 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 23 LFS241 Class Forum
- 26 LFS242 Class Forum
- 18 LFS243 Class Forum
- 4 LFS244 Class Forum
- 7 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 103 LFS253 Class Forum
- 751 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 48 LFS260 Class Forum
- 74 LFS261 Class Forum
- 6 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 8 LFS268 Class Forum
- 4 LFS269 Class Forum
- 173 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 184 LFW211 Class Forum
- 99 LFW212 Class Forum
- 875 Hardware
- 204 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 716 Linux Distributions
- 78 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 125 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 344 Ubuntu
- 445 Linux System Administration
- 33 Cloud Computing
- 63 Command Line/Scripting
- Github systems admin projects
- 88 Linux Security
- 73 Network Management
- 105 System Management
- 45 Web Management
- 50 Mobile Computing
- 18 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 499 Off Topic
- 119 Introductions
- 193 Small Talk
- 19 Study Material
- 742 Programming and Development
- 237 Kernel Development
- 471 Software Development
- 898 Software
- 244 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 313 Installation
- 19 All In Program
- 19 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)