Skip to content

Latest commit

 

History

History
156 lines (151 loc) · 29.3 KB

reading-list.md

File metadata and controls

156 lines (151 loc) · 29.3 KB

1990-1999

  • Eugene H Spafford and Stephen A Weeber. Software Forensics: Can we track code to its authors?. Technical Report CSD-TR 92-010, Purdue, 19 February 1992.
    • Section 2.1 discusses features in compiled code: Data Structures and Algorithms, Compiler and System Information, Programming skill and System knowledge, Choice of System Calls (aka libraries and APIs), and Errors.
    • Section 2.2 discusses features in source code and may be applicable to scripting languages: (several not included here...), Use of language features, Scoping, Execution paths, Bugs, and Metrics.
    • Sections 3 and 4 discuss some of the problems that may be encountered with authorship analysis, such as code reuse and multi-author code projects.
  • David B Hull. Computer Viruses: Naming and Classification. Virus Bulletin, September 1995.
    • discussion of classification approaches, evolution and non-evolution changes
    • relevant article that references this and other early work
  • Ivan Krsul and Eugene H. Spafford. Authorship analysis: Identifying the author of a program. Computers & Security 16, no. 3 (1997): 233-257.
  • Diego Doval, Spiros Mancoridis, and Brian S. Mitchell. Automatic clustering of software systems using a genetic algorithm. Proceedings of Software Technology and Engineering Practice (STEP'99), IEEE, 1999.
    • The goal in this paper appears to be to chunk large software systems into "like" components, making them easier to analyze. They do this by using genetic algorithms and module-dependency graphs, or control flow graphs.
    • Data used for testing includes: "Mini-Tunis, the RCS source code control system, a Turing compiler, the ispell spell checking tool, the Boxer graphical editor, and the Bison compiler-compiler."

2000-2009

2010-2012

2013-2015

2016-2018

2019-2021