Chapter 1: Introduction to Command Line

Chapter1
Introduction to Command Line
1
Dr. Hadeel Alazzam
Scripting Programming
1

2
• Textbook
• The Command Line
• Why Bash?
• Command-Line Illustrations
• Running Linux and bash on Windows
• Command-Line Basics
• Practical Examples
Outline

3
Text Book
• Paul Troncone (2019). Cybersecurity Ops with bash:
Attack, Defend, and Analyze from the Command Line,
First Edition

4
Command Line
• The command line is a text interface for your computer.
• Like Windows Explorer on Windows or Finder on Mac OSX it lets you navigate through the files
and folders of your computer, but it is completely text based.
• A computer’s command-line interface (CLI) gives you an intimate
connection with its operating system (OS).
• Command-line interfaces are also called command-line user
interfaces, console user interfaces and character user interfaces.
• The command line is a powerful tool that can significantly speed up
your workflow but can also irreversibly harm your computer so make
sure you use it responsibly.

Why Command Line?
• The ability to effectively use the command line is a critical skill for
security practitioners and administrators.
• Many tools of the trade such as Metasploit, Nmap, and Snort require
command-line proficiency simply to use them.
• During penetration testing, your only option may be to use a command-
line interface when interacting with a target system, particularly in the
early stages of an intrusion.
5
Dr.AryafAl-adwan,AutonomousSystemsDept 5

Command Line Primer
6
Dr. Aryaf Al-adwan, Autonomous
Systems Dept
• The term command line is used to refer to all of the
various non-GUI executables installed with an operating
system, along with, and especially, the built-ins,
keywords, and scripting capabilities available from the
shell — its command-line interface.
• To effectively utilize the command line, you need two
things:
• An understanding of the features and options of the existing
commands.
• A way to sequence commands together by using a scripting
language.
6

Command Line Primer
7
Systems Dept
• In this course, we introduce more than 40 commands
that span both the Linux and Windows operating
systems, as well as a variety of shell built-ins and
keywords.
• Most of the commands introduced originate from the
Linux environment, but as you will see, there are
multiple methods for running them on Windows
platforms.
7

Why Bash?
8
Systems Dept
• For scripting purposes, we choose the bash shell and
command language.
• The bash shell has been around for decades.
• Bash is available in nearly every version of Linux, and
has even permeated the Windows operating system
(Cross-platform).
• The proliferation of bash gives offensive operators and
penetration testers a particular advantage.
• Because in many cases there is no additional supporting
infrastructure or interpreters to install on a target system.
8

Command-Line Illustrations
9
Systems Dept
• A single-line command illustration will appear as follows:
• If the single-line command illustration also displays output, it will
appear as follows:
• The leading $ character is not part of the command, but is meant to
represent the simple prompt of the shell command line.
• It is shown to help you differentiate between the command (as you
would type it) and its output to the terminal.
9

Running Linux and bash on
Windows
1
0
Systems Dept
• The four options to run Linux and bash on Windows:
• Git Bash
• Cygwin
• The Windows Subsystem for Linux,
• Windows Command Prompt and PowerShell.
10

Git Bash
1
1
Systems Dept
• You can run many standard Linux commands
and the bash shell in the Windows environment
if you have installed Git, which includes a port
of bash.
• You can download Git from Git Website here.
• Once it’s installed, you can run bash by right-
clicking on the desktop or in a folder and
selecting Git Bash Here.
• https://gitforwindows.org/
11

Git Bash
1
2
Systems Dept
12

Cygwin
1
3
Systems Dept
• Cygwin is a full-featured Linux emulator that
also includes the ability to install a variety of
packages.
• It is similar to Git Bash in that it allows calling
many native Windows commands in addition to
the standard Linux commands.
• Cygwin can be downloaded from the project
website.
• https://www.cygwin.com/
13

Command-Line Basics
1
4
Systems Dept
• One of the basic operations of bash is to execute a command — that
is, to run another program.
• When several words appear on the command line, bash assumes that the first
word is the name of the program to run and the remaining words are the
arguments to the command.
• For example, to have bash run the command called mkdir and to pass it two
arguments -p and /tmp/scratch/garble, you would type this:
mkdir -p /tmp/scratch/garble
• By convention, programs generally have their options located first, and have them
begin with a leading -, as is the case here with the -p option.
• This particular command is being told to create a directory called
/tmp/scratch/garble.
• The -p option indicates that no errors will be reported and any intervening directories
will be created (or attempted) as needed
• (e.g., if only /tmp exists, then mkdir will first create /tmp/scratch before
attempting to create /tmp/scratch/garble).
14

Commands, Arguments, Built-ins, and
Keywords
1
5
Systems Dept
• The pwd command prints out the current directory you are in.
• The ls command prints out the contents of a directory.
• ls –a àlist hidden files
• ls –l à list files in current directory with permissions.
• The cd command allows you to move between directories.
• The mkdir creates directories.
• The touch used to create files.
• Don’t forget to specify what kind of file you are creating: for
example, touch index.html
• You can use the type command to identify whether a word is a
keyword, a built- in, a command, or none of those.
• The -t option keeps the output to a single word:
15

Commands, Arguments, Built-ins, and
Keywords
1
6
Systems Dept
• You can use the compgen command to determine what commands,
built-ins, and keywords are available to you.
• Use the -c option to list commands, -b for built- ins, and -k for
keywords.
16

Standard Input/Output/Error
1
7
Systems Dept
• A running program is called, in operating systems, a process.
• Every process in the Unix/Linux/POSIX (and thus Windows)
environment has three distinct input/output file descriptors:
• These three are called standard input (or stdin)
• Standard output (stdout)
• Standard error (stderr)
17

Redirection and Piping
1
8
Systems Dept
• If you have a program called handywork that reads its input from stdin
and writes its results to stdout, you can change its behavior as simply
as this:
• This will run handywork but will have the input come not from the
keyboard but instead from the data file called data.in
• Similarly, the output is being sent not to the screen but into a file called
results.out
• The file will be created if it doesn’t exist and overwritten if it does
• This technique is called redirection because we are redirecting input
to come from a different place and redirecting output to go somewhere
other than the screen.
18

Stderr
1
9
Systems Dept
• We have to distinguish between stdout and stderr when redirecting data
coming out of the program.
• We make this distinction through the use of the file descriptor
numbers:
• stdin is file descriptor 0
• stdout is file descriptor 1
• stderr is file descriptor 2
• You can redirect error messages as follows:
• This redirects only stderr and sends any such error message output to
a file we call err.msgs
• Of course, we can do all three on the same line:
19

2
0
Systems Dept
• If you want the error messages combined with the normal output, you can
do this with the following syntax:
• You can use the shorthand command as follows:
• If you want to discard standard output, you can redirect it to a special
file called /dev/null as follows:
• To view output on the command line and simultaneously redirect that
same output to a file, use the tee command.
20

2
1
Systems Dept
• Use the -a option on the tee command to append to its output file rather
than overwrite it.
• The | character is known as a pipe.
• It allows you to take the output from one command or script and
provide it as input into another command.
• In this example, the output of handywork is piped into the tee
command for further processing.
• A file will be created or truncated (i.e., content discarded) when output
is redirected using the single greater-than (>) sign.
• If you want to preserve the file’s existing content, you can, instead,
append to the file by using a double greater- than (>>) sign, like this:
21

2
2
Systems Dept
• If you want appends both stdout and stderr to the file results.out rather
than overwriting its existing content.
22

Running Commands in the Background
2
3
Systems Dept
• In this course, we will be going beyond one-line commands and will be
building complex scripts.
• Some of these scripts can take a significant amount of time to execute, so
that you may not want to spend time waiting for them to complete.
• Instead, you can run any command or script in the background by using
the & operator.
• The script will continue to run, but you can continue to use the shell to
issue other commands and/or run other scripts.
• You will likely want to redirect both standard output and/or standard
error to a file when sending tasks to the background:
23

Running Commands in the Background
2
4
Systems Dept
• You can use the jobs command to list any tasks currently running in the
background:
• Use the fg command and the corresponding job number to bring the task
back into the foreground:
• If your task is currently executing in the foreground, you can use Ctrl-Z to
suspend the process and then bg to continue the process in the
background.
• From there, you can use jobs and fg as described previously.
24

From Command Line to Script
2
5
Systems Dept
• A shell script is just a file that contains the same commands that you
could type on the command line.
• Put one or more commands into a file and you have a shell script.
• If you called your file myscript, you can run that script by typing bash
myscript or you can give it execute permission(e.g.,chmod 755 myscript).
• You can invoke it directly to run the script: ./myscript
• We often include the following line as the first line of the script, which
tells the operating system which scripting language we are using:
• Of course, this assumes that bash is located in the /bin directory.
• If your script needs to be more portable, you could use this approach
instead:
• It uses the env command to look up the location of bash and is
considered the standard way to address the portability problem.
25

Lab Exercises
2
6
Systems Dept
26

End
27
Dr. Aryaf Al-adwan, Autonomous Systems Dept 27

Chapter 1: Introduction to Command Line

More Related Content

Similar to Chapter 1: Introduction to Command Line

Recently uploaded

Chapter 1: Introduction to Command Line