Recent Changes - Search:

CSE dept.


This site contains wiki-pages for the department of computer science and engineering at Chalmers and GU.


edit SideBar

Sec

(One of the Course Clusters.)

  • Sec = Security
    • Sec Chair AnSa, Co-chair KaMi@NS, DaHe, ...
    • Sec: Computer Security (@NS)
    • Sec: Cryptography (@ST)
    • Sec: Language-based security (@ST)
    • Sec: Network security (@NS)

Security specialization meeting 2014-03-21

  • Present - the course responsible for the course in the security specialization
    • Magnus Almgren (CS)
    • Tomas Olovsson (NS)
    • Katerina Mitrokotsa (Crypto)
    • Andrei Sabelfeld (LBS)
  • Computer Security: LP3
    • Started 1993
    • 2014: 129 ppl
    • Prereq OS
    • Labs:
      • Login
      • PGP --> crypto
      • SQL --> LBS
      • Scanning (high level, report) --> NS
  • Network Security: LP4
    • Started 2005
    • 2014: roughly 80
    • Prereq: communication, CS?
    • Labs:
      • Scanning (low level)
      • Firewall (report)
      • IDS (Snort)
      • SL/TLS
  • Language-based security: LP4
    • Started 2005
    • 2014: roughly 50--80
    • Prereq: some basic computer science, but not formal
    • Labs:
      • Races (TOCTOU in Java)
      • Buffer overrun
      • Web application security: SQL injection, cross-site scripting) + how to fix
      • Projects (Android security, CSRF, ) Project will give grade. No exam.
  • Crypto: LP2/LP6
    • Started 1993
    • 2014: 120 students
    • Prereq: programming course, some background on math, GU: Discreet math
    • Labs:
      • Math assignment: protocol attack, freshness of protocol, RSA?
      • Implementation of some crypto problem, SAGE, RSA
      • Related to the second, implementation crypto
  • Substitutes
    • CS: Tomas, Katerina
    • LBS: Dave
    • Crypto: Aysajah, Andrei
    • NS: Magnus
  • Discussion about order of courses, placements, problems with tracks, etc.
    • Conclusion: For the specialization to be portable to Master's programs, it is important that the Master's programs do not have too rigid requirements on course sequence, tracks, etc.
    • Action: bring up the portability issue with people in charge
    • Action: coordinate with real-time track to see if they experience similar questions
Edit - History - Print - Recent Changes - Search
Page last modified on March 26, 2014, at 12:47 PM