User Tools

Site Tools


haas:spring2016:unix:projects:udr2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:spring2016:unix:projects:udr2 [2016/03/21 15:19] – [Useful tools] wedgehaas:spring2016:unix:projects:udr2 [2016/03/24 17:40] (current) – [Errata] wedge
Line 11: Line 11:
 Typos and bug fixes: Typos and bug fixes:
  
-  * <description> (DATESTAMP)+  * A bug was discovered in binhaxx/search, which caused it to erroneously skip nearby packets when doing a complete packet search. This has been fixed and a new version of binhaxx has been released (1.0.1). Be sure to grab the updated version and use that. (20160324)
 =====Objective===== =====Objective=====
 Continuing our "1337 haxxing" series of projects, we've found considerable conceptual self-imposed roadblocks blocking our employment of otherwise simple computing properties (that not only is **everything a file**, but that files are fundamentally a series of bytes). The sooner we accept this truth, the sooner many challenges begin to vanish. Continuing our "1337 haxxing" series of projects, we've found considerable conceptual self-imposed roadblocks blocking our employment of otherwise simple computing properties (that not only is **everything a file**, but that files are fundamentally a series of bytes). The sooner we accept this truth, the sooner many challenges begin to vanish.
Line 232: Line 232:
  
 **NOTE:** Hopefully it has been standard practice to locate project files in their own unique subdirectory, such as under **src/unix/**, where you can then add/commit/push the results to your repository (you ARE regularly putting stuff in your repository, aren't you?) **NOTE:** Hopefully it has been standard practice to locate project files in their own unique subdirectory, such as under **src/unix/**, where you can then add/commit/push the results to your repository (you ARE regularly putting stuff in your repository, aren't you?)
 +
 +**NOTE:** You probably do not want to add/commit/push this **sleepfun.tar.bz2** archive, nor its extracted **.raw** files, as they do consume a bit of space. 
  
 =====Data Files===== =====Data Files=====
Line 281: Line 283:
 ... along with other tools previously encountered. ... along with other tools previously encountered.
  
-====bgrep==== +====binhaxx search==== 
-To assist you with this project, a special "binary grep" has been deployed on the system, called **bgrep**. bgrep searches for patterns among binary data, as part of STDIN.+To assist you with this project, a special "binary search" has been developed, provided via the **binhaxx** tools, called **search**. **search** searches for patterns among binary data, as part of STDIN.
  
-It supports space-separated (or not) bytes of data, and even allows the use of '.' to denote any hex value (remember, it takes 2 hex values to occupy a byte).+It supports space-separated bytes of data, and even allows the use of '.' to denote any hex value (remember, it takes 2 hex values to occupy a byte).
  
 ===Example Usage=== ===Example Usage===
Line 290: Line 292:
  
 <cli> <cli>
-$ cat session-201302200614.raw | bgrep '12 34' +$ cat session-201302200614.raw | search '12 34' 
 533b:12 34  533b:12 34 
 29af3:12 34  29af3:12 34 
Line 308: Line 310:
  
 <cli> <cli>
-$ cat session-201302200614.raw | bgrep '12 .. 45' +$ cat session-201302200614.raw | search '12 .. 45' 
 3326:12 e0 45 3326:12 e0 45
  
Line 318: Line 320:
  
 <cli> <cli>
-$ cat session-201302200614.raw | bgrep '12 e.' +$ cat session-201302200614.raw | search '12 e.' 
 1cf4:12 ee  1cf4:12 ee 
 206d:12 e0  206d:12 e0 
Line 352: Line 354:
  
 <cli> <cli>
-$ cat session-201302200614.raw | bgrep '.c34+$ cat session-201302200614.raw | search '.c 34
 91c1:3c 34  91c1:3c 34 
 29029:8c 34  29029:8c 34 
Line 362: Line 364:
  
 </cli> </cli>
- 
-Notice in this last pattern, we opted not to space separate the pattern... it works either way (output will be space-separated regardless). 
  
 This will hopefully prove to be a useful tool in your binary analysis endeavors. This will hopefully prove to be a useful tool in your binary analysis endeavors.
 +
 =====Submission===== =====Submission=====
 Successful completion will result in the following criteria being met: Successful completion will result in the following criteria being met:
  
-  * When all is said and done, you will submit: +  * When all is said and done, you will submit 2 files
-    * **udr2.text**, containing the answers/responses to all the above questions (including commands used to pull off the project)+    * **udr2.text**, containing
 +      * an organized presentation of the answers/responses to all the above questions 
 +    * **udr2.sh** 
 +      * a shell script containing all the necessary commands to accomplish the project (and will automate a run of the project when executed). 
 +      * be sure to adequately comment the script so I can see your thought process (particular commands used, options utilized, logic used). 
 +      * the script should output important information related to the particular step being taken ("Determining amount of Deep Sleep", "Determining total time spent asleep", etc.), along with the determined result of that particular data point.
 ====Submit==== ====Submit====
 Please submit as follows: Please submit as follows:
  
 <cli> <cli>
-lab46:~/src/unix/udr2$ submit unix udr2 udr2.text+lab46:~/src/unix/udr2$ submit unix udr2 udr2.text udr2.sh
 Submitting unix project "udr2": Submitting unix project "udr2":
     -> udr2.text(OK)      -> udr2.text(OK) 
 +    -> udr2.sh(OK)
  
 SUCCESSFULLY SUBMITTED SUCCESSFULLY SUBMITTED
 lab46:~/src/unix/udr2$  lab46:~/src/unix/udr2$ 
 </cli> </cli>
 +
haas/spring2016/unix/projects/udr2.1458573572.txt.gz · Last modified: 2016/03/21 15:19 by wedge