Franske ITC-2480 Lab 3 - Revision history

BenFranske: /* Install the Webmin Control Panel */

2021-09-29T19:50:13Z

Install the Webmin Control Panel

← Older revision		Revision as of 19:50, 29 September 2021
Line 129:		Line 129:
	<li> Notice the additional packages which are required by Webmin (dependencies) which will be downloaded and installed by '''apt''' from a repository in order to complete the installation.</li>		<li> Notice the additional packages which are required by Webmin (dependencies) which will be downloaded and installed by '''apt''' from a repository in order to complete the installation.</li>
	<li> Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx</li>		<li> Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx</li>
			: ''NOTE: You will receive a certificate error when you connect to this site because the default Webmin SSL certificate is self-signed. Some browsers will allow you to bypass this error and connect to the untrusted site anyway. Some browsers, in particular Chrome, may not allow the connection. In that case you will need to use a different browser which allows you to bypass the insecure certificate warning or update the Webmin SSL certificate. In most cases it will be easier for our lab purposes to just use a different browser.''
	<li> Login using your Debian username and password </li>		<li> Login using your Debian username and password </li>
	<li> Explore the Webmin interface		<li> Explore the Webmin interface

BenFranske: Update to mjnk version

2021-08-25T02:49:12Z

Update to mjnk version

Show changes

BenFranske: /* Install the Webmin control panel */

2018-01-22T05:56:02Z

Install the Webmin control panel

← Older revision		Revision as of 05:56, 22 January 2018
Line 37:		Line 37:
	# Use the links browser to download the DEB package file from www.webmin.com		# Use the links browser to download the DEB package file from www.webmin.com
	# Because this DEB file was downloaded directly instead of automatically by APT from a package repository the installation command is slightly different and some other commands such as '''apt show''' will not work. Install the package with '''apt install ./''<filename.deb>''''' Don't forget that installation of software must be done with system administrator permissions.		# Because this DEB file was downloaded directly instead of automatically by APT from a package repository the installation command is slightly different and some other commands such as '''apt show''' will not work. Install the package with '''apt install ./''<filename.deb>''''' Don't forget that installation of software must be done with system administrator permissions.
	#* NOTE: You can get similar information to what you can get with '''apt show''' from a DEB package file using '''dpkg -I '''<filename>'''''		#* NOTE: You can get similar information to what you can get with '''apt show''' from a DEB package file using '''dpkg -I ''<filename>'''''
	# Notice the additional packages which are required by Webmin (dependencies) which will be downloaded and installed by APT from a repository in order to complete the installation.		# Notice the additional packages which are required by Webmin (dependencies) which will be downloaded and installed by APT from a repository in order to complete the installation.
	# Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx		# Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx
	# Explore the webmin interface		# Explore the webmin interface

BenFranske: /* Practice Linux filesystem permissions and ownership */

2018-01-20T05:38:35Z

Practice Linux filesystem permissions and ownership

← Older revision		Revision as of 05:38, 20 January 2018
Line 21:		Line 21:

	== Practice Linux filesystem permissions and ownership ==		== Practice Linux filesystem permissions and ownership ==
	* NOTE: Working with file and directory ownership and permissions is tricky and there are many, many possible combinations of users, groups, and permissions which can be assigned to both files and folders. The goal of this section of the lab is to familiarize you with how to use the commands for changing ownership and permissions, not to teach you how to read or understand Linux file permissions (see your readings for this, it is important!) Once you understand how to use the commands you should experiment with setting different owners and permissions on a several different files and folders and subfolders until you have a good understanding of how permissions work. The only way to understand these relationships well is to try it out. You should be able to set all of these permissions just as regular users (assuming you have access to both of the user accounts) you should not need sudo access to change the permissions because one of the the two users owns all the files and directories we're working in. You will need sudo access to change the owner of the files because otherwise it would be possible to accidentally lock yourself out of a file.		* NOTE: Working with file and directory ownership and permissions is tricky and there are many, many possible combinations of users, groups, and permissions which can be assigned to both files and folders. The goal of this section of the lab is to familiarize you with how to use the commands for changing ownership and permissions, not to teach you how to read or understand Linux file permissions (see your readings for this, it is important!) Once you understand how to use the commands you should experiment with setting different owners and permissions on a several different files and folders and subfolders until you have a good understanding of how permissions work. The only way to understand these relationships well is to read about it and then try it out. You should be able to set all of these permissions just as regular users (assuming you have access to both of the user accounts) ''you should not need sudo access to change the permissions because one of the the two users owns all the files and directories we're working in. You will need sudo access to change the owner of the files because otherwise it would be possible to accidentally lock yourself out of a file.''
	# Change to the ''/home'' directory and check the ownership and permissions on the subdirectories inside of ''/home''		# Change to the ''/home'' directory and check the ownership and permissions on the subdirectories inside of ''/home''
	# Try to create new files using the '''touch''' command called ''foo'' and ''foo2'' in the ''/home/jsmith'' directory as both your regular user and as ''jsmith'' respectively		# Try to create new files using the '''touch''' command called ''foo'' and ''foo2'' in the ''/home/jsmith'' directory as both your regular user and as ''jsmith'' respectively

BenFranske: /* Practice Linux filesystem permissions and ownership */

2018-01-20T05:37:23Z

Practice Linux filesystem permissions and ownership

← Older revision		Revision as of 05:37, 20 January 2018
Line 21:		Line 21:

	== Practice Linux filesystem permissions and ownership ==		== Practice Linux filesystem permissions and ownership ==
	* NOTE: Working with file and directory ownership and permissions is tricky and there are many, many possible combinations of users, groups, and permissions which can be assigned to both files and folders. The goal of this section of the lab is to familiarize you with how to use the commands for changing ownership and permissions. Once you understand how to use the commands you should experiment with setting different owners and permissions on a several different files and folders and subfolders until you have a good understanding of how permissions work. The only way to understand these relationships well is to try it out. You should be able to set all of these permissions just as regular users (assuming you have access to both of the user accounts) you should not need sudo access to change the permissions because one of the the two users owns all the files and directories we're working in. You will need sudo access to change the owner of the files because otherwise it would be possible to accidentally lock yourself out of a file.		* NOTE: Working with file and directory ownership and permissions is tricky and there are many, many possible combinations of users, groups, and permissions which can be assigned to both files and folders. The goal of this section of the lab is to familiarize you with how to use the commands for changing ownership and permissions, not to teach you how to read or understand Linux file permissions (see your readings for this, it is important!) Once you understand how to use the commands you should experiment with setting different owners and permissions on a several different files and folders and subfolders until you have a good understanding of how permissions work. The only way to understand these relationships well is to try it out. You should be able to set all of these permissions just as regular users (assuming you have access to both of the user accounts) you should not need sudo access to change the permissions because one of the the two users owns all the files and directories we're working in. You will need sudo access to change the owner of the files because otherwise it would be possible to accidentally lock yourself out of a file.
	# Change to the ''/home'' directory and check the ownership and permissions on the subdirectories inside of ''/home''		# Change to the ''/home'' directory and check the ownership and permissions on the subdirectories inside of ''/home''
	# Try to create new files using the '''touch''' command called ''foo'' and ''foo2'' in the ''/home/jsmith'' directory as both your regular user and as ''jsmith'' respectively		# Try to create new files using the '''touch''' command called ''foo'' and ''foo2'' in the ''/home/jsmith'' directory as both your regular user and as ''jsmith'' respectively

BenFranske: /* Create Linux users and groups */

2018-01-20T05:33:16Z

Create Linux users and groups

← Older revision		Revision as of 05:33, 20 January 2018
Line 12:		Line 12:
	# Add the ''jsmith'' account as well as your own user account to the ''redteam'' group		# Add the ''jsmith'' account as well as your own user account to the ''redteam'' group
	# In order for your user accounts to receive their new group permissions they need to be logged back in so close your SSH session and open two new SSH sessions, login as your regular user on one and ''jsmith'' on the other		# In order for your user accounts to receive their new group permissions they need to be logged back in so close your SSH session and open two new SSH sessions, login as your regular user on one and ''jsmith'' on the other
	# View a list of all the user accounts on your system by looking at the ''/etc/passwd'' file which is a plain text file on your system.		# View a list of all the user accounts on your system by looking at the ''/etc/passwd'' file which is a plain text file on your system. To output the contents of the ''/etc/passwd'' file you can use the '''cat /etc/passwd''' command
	## To output the contents of the /etc/passwd file you can use the '''cat /etc/passwd''' command		# View a list of the password data on your system by viewing the ''/etc/shadow'' file
	## To output the contents of the file while pausing after each page of output use the '''more /etc/~~passwd~~''' command		# View a list of groups and group members on your system in the ''/etc/group'' file
	## To output the contents of the file while pausing after each page of output and being able to scroll up and down through the output use the '''less /etc/~~passwd~~''' command and press q to return to the command line		#* NOTE: The group list may be longer than one full screen of text (the same is true of the ''/etc/passwd'' or ''/etc/shadow'' file depending on your screen resolution.
			#*# To output the contents of the file while pausing after each page of output use the '''more /etc/group''' command
			#*# To output the contents of the file while pausing after each page of output and being able to scroll up and down through the output use the '''less /etc/group''' command and press q to return to the command line
			#*# It may be helpful to try these commands to display an even longer text file like one of the Shakespeare texts you downloaded in an earlier lab in the ''~/sample-files'' directory. You may have to un-tar the files again first.

	== Practice Linux filesystem permissions and ownership ==		== Practice Linux filesystem permissions and ownership ==

BenFranske at 22:54, 15 January 2018

2018-01-15T22:54:41Z

BenFranske: /* Install the Webmin control panel */

2018-01-15T22:50:37Z

Install the Webmin control panel

← Older revision		Revision as of 22:50, 15 January 2018
Line 33:		Line 33:
	== Install the Webmin control panel ==		== Install the Webmin control panel ==
	# Use the links browser to download the DEB package file from www.webmin.com		# Use the links browser to download the DEB package file from www.webmin.com
	# ~~Use dpkg -i to install the webmin~~ DEB package		# Because this DEB file was downloaded directly instead of automatically by APT from a package repository the installation command is slightly different and some other commands such as '''apt show''' will not work. Install the package with '''apt install ./''<filename.deb>''''' Don't forget that installation of software must be done with system administrator permissions.
	~~# Make a note of~~ the ~~unmet dependencies for~~ the ~~webmin~~ package		#* NOTE: You can get similar information to what you can get with '''apt show''' from a DEB package file using '''dpkg -I '''<filename>'''''
	~~# Use aptitude or~~ apt~~-get to~~ install ~~the dependencies for webmin~~		# Notice the additional packages which are required by Webmin (dependencies) which will be downloaded and installed by APT from a repository in order to complete the installation.
	#* ~~Hint~~: You can ~~either install these based on the list of unmet dependencies or~~ you can ~~investigate the man page for~~ apt-~~get~~ and ~~take~~ a ~~look at~~ the ~~-f option or the apt --fix-broken install choice~~
	# Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx		# Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx
	# Explore the webmin interface		# Explore the webmin interface

BenFranske: /* Install the Webmin control panel */

2017-10-25T00:43:03Z

Install the Webmin control panel

← Older revision		Revision as of 00:43, 25 October 2017
Line 36:		Line 36:
	# Make a note of the unmet dependencies for the webmin package		# Make a note of the unmet dependencies for the webmin package
	# Use aptitude or apt-get to install the dependencies for webmin		# Use aptitude or apt-get to install the dependencies for webmin
	#* Hint: You can either install these based on the list of unmet dependencies or you can investigate the man page for apt-get and take a look at the -f option		#* Hint: You can either install these based on the list of unmet dependencies or you can investigate the man page for apt-get and take a look at the -f option or the apt --fix-broken install choice
	# Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx		# Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx
	# Explore the webmin interface		# Explore the webmin interface

BenFranske: /* Install the Webmin control panel */

2014-08-06T02:09:10Z

Install the Webmin control panel

← Older revision		Revision as of 02:09, 6 August 2014
Line 35:		Line 35:
	# Use dpkg -i to install the webmin DEB package		# Use dpkg -i to install the webmin DEB package
	# Make a note of the unmet dependencies for the webmin package		# Make a note of the unmet dependencies for the webmin package
	# Use aptitude to install the dependencies for webmin		# Use aptitude or apt-get to install the dependencies for webmin
			#* Hint: You can either install these based on the list of unmet dependencies or you can investigate the man page for apt-get and take a look at the -f option
	# Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx		# Open a web browser on your host system and visit https://xxx.xxx.xxx.xxx:10000 where your IP replaces xxx.xxx.xxx.xxx
	# Explore the webmin interface		# Explore the webmin interface

← Older revision		Revision as of 22:54, 15 January 2018
Line 8:		Line 8:

	== Create Linux users and groups ==		== Create Linux users and groups ==
	# Create a new user account "jsmith" using the adduser program		# Create a new user account ''jsmith'' using the '''adduser''' program
	# Create a new group "redteam" using the addgroup program		# Create a new group ''redteam'' using the '''addgroup''' program
	# Add the jsmith account as well as your own user account to the redteam group		# Add the ''jsmith'' account as well as your own user account to the ''redteam'' group
	# In order for your user accounts to receive their new group permissions they need to be logged back in so close your SSH session and open two new SSH sessions, login as your regular user on one and jsmith on the other		# In order for your user accounts to receive their new group permissions they need to be logged back in so close your SSH session and open two new SSH sessions, login as your regular user on one and ''jsmith'' on the other
	# View a list of all the user accounts on your system by looking at the /etc/passwd file which is a plain text file on your system.		# View a list of all the user accounts on your system by looking at the ''/etc/passwd'' file which is a plain text file on your system.
	## To output the contents of the /etc/passwd file you can use the "cat /etc/passwd" command		## To output the contents of the /etc/passwd file you can use the '''cat /etc/passwd''' command
	## To output the contents of the file while pausing after each page of output use the "more /etc/passwd" command		## To output the contents of the file while pausing after each page of output use the '''more /etc/passwd''' command
	## To output the contents of the file while pausing after each page of output and being able to scroll up and down through the output use the "less /etc/passwd" command and press q to return to the command line		## To output the contents of the file while pausing after each page of output and being able to scroll up and down through the output use the '''less /etc/passwd''' command and press q to return to the command line

	== Practice Linux filesystem permissions and ownership ==		== Practice Linux filesystem permissions and ownership ==
	* NOTE: Working with file and directory ownership and permissions is tricky and there are many, many possible combinations of users, groups, and permissions which can be assigned to both files and folders. The goal of this section of the lab is to familiarize you with how to use the commands for changing ownership and permissions. Once you understand how to use the commands you should experiment with setting different owners and permissions on a several different files and folders and subfolders until you have a good understanding of how permissions work. The only way to understand these relationships well is to try it out. You should be able to set all of these permissions just as regular users (assuming you have access to both of the user accounts) you should not need sudo access to change the permissions because one of the the two users owns all the files and directories we're working in. You will need sudo access to change the owner of the files because otherwise it would be possible to accidentally lock yourself out of a file.		* NOTE: Working with file and directory ownership and permissions is tricky and there are many, many possible combinations of users, groups, and permissions which can be assigned to both files and folders. The goal of this section of the lab is to familiarize you with how to use the commands for changing ownership and permissions. Once you understand how to use the commands you should experiment with setting different owners and permissions on a several different files and folders and subfolders until you have a good understanding of how permissions work. The only way to understand these relationships well is to try it out. You should be able to set all of these permissions just as regular users (assuming you have access to both of the user accounts) you should not need sudo access to change the permissions because one of the the two users owns all the files and directories we're working in. You will need sudo access to change the owner of the files because otherwise it would be possible to accidentally lock yourself out of a file.
	# Change to the /home directory and check the ownership and permissions on the subdirectories inside of /home		# Change to the ''/home'' directory and check the ownership and permissions on the subdirectories inside of ''/home''
	# Try to create new files using the touch command called foo and foo2 in the /home/jsmith directory as both your regular user and as jsmith respectively		# Try to create new files using the '''touch''' command called ''foo'' and ''foo2'' in the ''/home/jsmith'' directory as both your regular user and as ''jsmith'' respectively
	# Try removing the foo and/or foo2 files using both your regular user account and jsmith		# Try removing the ''foo'' and/or ''foo2'' files using both your regular user account and ''jsmith''
	# Use the jsmith user to create a new directory /home/jsmith/redteam/		# Use the ''jsmith'' user to create a new directory ''/home/jsmith/redteam/''
	# Use the jsmith user to create some files: /home/jsmith/redteam/theplan and /home/jsmith/redteam/yours /home/jsmith/redteam/mine and /home/jsmith/ours		# Use the ''jsmith'' user to create some files: ''/home/jsmith/redteam/theplan'' and ''/home/jsmith/redteam/yours'' ''/home/jsmith/redteam/mine'' and ''/home/jsmith/ours''
	# In order to find out more about the chown and chgrp programs which you'll use to change the owners and groups for files and directories use the "man chown" and "man chgrp" commands to view the built in manual pages. Almost every command line tool in Linux has a manual page you can view in this way, try accessing a few other man pages for some of the other tools we've been using. You can scroll through the manual pages using the arrow keys and page up/down. To return to the command line press the q key.		# In order to find out more about the chown and chgrp programs which you'll use to change the owners and groups for files and directories use the '''man chown''' and '''man chgrp''' commands to view the built in manual pages. Almost every command line tool in Linux has a manual page you can view in this way, try accessing a few other man pages for some of the other tools we've been using. You can scroll through the manual pages using the arrow keys and page up/down. To return to the command line press the q key.
	# Change the permissions on the /home/jsmith/redteam/ directory so that the group "redteam" is the group owner of the directory		# Change the permissions on the ''/home/jsmith/redteam/'' directory so that the group ''redteam'' is the group owner of the directory
	# Add write permission for the group to the /home/jsmith/redteam/ directory		# Add write permission for the group to the ''/home/jsmith/redteam/'' directory
	# Change the ownership of the yours file so that it is owned by your regular user account instead of jsmith		# Change the ownership of the yours file so that it is owned by your regular user account instead of ''jsmith''
	# Change the group owner of the ours file so that it is controlled by the redteam group		# Change the group owner of the ours file so that it is controlled by the ''redteam'' group
	# Experiment with creating and removing files and subdirectories inside of the /home/jsmith/redteam/ directory as well as listing the contents of directories with various permissions applied to them until you have a good understanding of how permissions work.		# Experiment with creating and removing files and subdirectories inside of the ''/home/jsmith/redteam/'' directory as well as listing the contents of directories with various permissions applied to them until you have a good understanding of how permissions work.

	== Install the Webmin control panel ==		== Install the Webmin control panel ==