A1 submission checklist: (in a1.zip)

a1/README.txt - contains student names and
a copy of this checklist with check marks across each line indicating which files were submitted.

a1/v3/
  makeShellCode.pl # modified so that it exploits v3
  stack.txt        # the picture of the stack

a1/functionPointer/
  makeBadInputA # a program generating the bad input leading to the exploit for part A
         # include a brief discussion of the vulnerability and
         # how you exploit it

  makeBadInputB # a program generating the bad input leading to the exploit for part B
         # include a brief discussion of the vulnerability and
         # how you exploit it

  makeBadInputC # a program generating the bad input leading to the exploit for part C
         # or an explanation of why this is not possible
         # if it is vulnerable, include a brief discussion of the vulnerability and
         # how you exploit it

  functionPointer.c # a fixed version of the program, please
         # discuss what you did to fix it in the code.

  functionPointer_bad.c # the original version of the program

a1/vulnerable/
  account_bad.c # the old, vulnerable version of the program
  account.c # this is the fixed version of the program
  README.txt # installation instructions
  accounts
  log
  passwords
  REPORT.txt # this is the file containing a report of vulnerabilities, 
  # exploits and impact, see the sample file

  # any other files you need to make your new program work

a1/vulnerable/exploits/
  # a collection of exploits for the account system
  # we should be able to run these against our original installation
  e1
  e2
  e3 
  ...

a1/palindrome/
  answers.txt
  tcpclientA.pl
  palindrome.c # the fixed version of the palindrome program
  palindrome_bad.c # the original version of the palindrome program
  palindrome.xinetd
  REPORT.txt 
  # any other files needed

-----------

I do want each folder to contain the original and modified code, so I
could easily run diff for comparison if needed.