homework 2: Inspecting Running Processes

The Challenge!

In the last homework you looked at the symbol table of your own compiled program. This time we’ll be watching and interacting with precompiled programs as they execute.

Before you start, please make sure to log in systems1.cs.uic.edu.

The skeleton code for this assignment is available at this link. You must use GitHub classroom to write your code and keep a commit log on GitHub. You can submit your code via Gradescope.

Your task will be to fill out two files in your personal repository called secrets.txt and howto.txt.

The format for secrets.txt should be:

0. these  
1. are  
2. not  
3. real  
4. secrets  

howto.txt is also required: you must describe in English how to find the secret for that given executable. Each individual howto should be on one more more lines after a line with only the executable number and a period on it, like so:

0.  
This was the really easy one. You had to run it and then type in the secret of life.  
1.  
For this one, I had to:  
* Run a specific unix utility to learn some specific information  
* Perform some specific task that I found out about by checking part of a specific line in the output of the unix utility.  
...

Your howto.txt should enable any other CS 361 student to find the password within a minute of reading it.

Warning

You must complete this assignment on systems1.cs.uic.edu. Failure to do so will result in a zero.

You will be given any other files to complete secret findings except the 5 executable files.

Hints:

Open your howto.txt alongside your shell as you work on each puzzle, and use it to take notes. If you don’t give a full description of how to arrive at the answer, you may not receive points.

The content of lab section will be incredibly helpful for this assignment. If you miss it, ask someone that went if they’re willing to share their notes with you.

Template

The skeleton code is available above. You can merge it into your personal repository to receive the relevant files in the correct directories.

Turn-in instructions

Same as before, you must push your code to gradescope. There is no autograder; correct answers will be self-evident for the secrets, and the howto.txt will be graded by hand.

Grading

Please be consistent with above formats; if you do not fill secrets.txt out exactly as directed, we will not give points back for bad formatting. howto.txt will be graded manually. If you do not complete your assignment on systems1.cs.uic.edu, you will receive no credit for the assignment.

The first 4 are each worth 1 point each, the final one is worth 4 points. An additional 2 points will be given for each correct howto.

Due Date

This assignment is due Monday, October 1st, at 11:59 PM. See the syllabus for the late turnin policy. This assignment is worth just as much as every other homework, so getting as much credit on it as possible is important (don’t turn it in late!).