Course feedback

[mosbth]

Notes on what to improve and change in the course. Mainly my own notes but feel free to add your own thoughts.

General

• Material for S0X and A0X could be combined into one page/article/module item on Canvas.

• There would be several opportunities to provide lecture material on the form of small videos explaining some concepts, extra work, perhaps aim at the hard parts and extra parts that is not covered in class.

• Pros of putting all course module descriptions on the wiki or github pages?

• Be more precise where to store the work/ to make it easy to auto correct.

• Grade 5 on A01/09 should be three 5 and one 4.

• Easier to grade several small assignments and most likely get a better quality of the submissions (compared to a large subsmission at the end of the course).

• Review all assignments and make them easier to submit and grade.

  • Where the code should be stored.
  • github.txt
  • githubpages.txt
  • Script to check that work/ complie with the assignments.
  • A06, A08, A09 should perhaps have their own report with a template, to keep it separate from the report page with the questions? Maybe.

S03/A03

• Deal with fetch issues, provide a REST server that can be used allowing CORS.
• Move duck should be done using JavaScript (not CSS).
• Enhance the flags to be exact in shape and form.

S04 Node

• R4 add the actual lotto draw to the response.
• Mixing caps makes it fail on Unix.

S05 PHP

• Perhaps show off a framework and how to use it.
• Write more code like a framework/view.
• Misintepretated the search.php assignment, perhaps add that to R4?
• The assignment could be a bit harder, so the requirements can not be solved "purely" by the example programs.
• The config.php must be stored in a specific path to be editable, or it must contain specifics on how to test the database.
• To all assignmnets, add "how to test".

S07/A07

• Add code sample on HTML forms.
• Add example on [FromForm] and [FromBody].
• Perhaps add some more beginner friendly code.
• Check "bug" when add account, move money and write to json (Truncate or WriteAll).
• Search must work on other systems.
• Path to data.json fails.

S08/A08

• A bit more instruction on what to look for in the three tools.

S09/A09

• Should/could have some laboratory part, perhaps just a session in class where we could train "hands on" on some common exploits.
• Laboratory parts could be CTF for the fun of it.
• Laboratory could be https://github.com/ethicalhack3r/DVWA (run in Docker).
• Lecture could be a tad more focused ib code samples i different languages on the most basic ways of protecting oneself, perhaps also att small example programs, 101 to code secure.

S10

• Project topic could be freely choosen, perhaps it would be better with o more defined topic, it would be easier to grade, but perhaps less fun for students who likes to choose freely.