README: keep track of the common thread
This commit is contained in:
parent
dc467108fa
commit
e69951fe71
1 changed files with 25 additions and 0 deletions
25
README.md
25
README.md
|
@ -1 +1,26 @@
|
|||
# Using Static Code Analysis To Improve Kernel-Task Memory-Safety
|
||||
|
||||
# Simple Motivational Golden Circle
|
||||
* Describes what this project is about very briefly
|
||||
* Helps to keep track of the goals
|
||||
|
||||
## Who?
|
||||
* Primariliy: OS Software Developers
|
||||
* Secondary: End Users
|
||||
|
||||
## Why?
|
||||
* The Linux/C/C++ software is full of vulnerabilities
|
||||
* A human solution is not reliable:
|
||||
- Developers make mistakes anyway!
|
||||
* C/C++ Compilers allow too many mistakes
|
||||
* Hardware-supported memory-management with stack/heap is hard to implement safely
|
||||
* Rust is a promising language
|
||||
|
||||
## How?
|
||||
* Look for a *technical* solution for these issues by first analyzing the status quo:
|
||||
- Which popular systems are most vulnerable?
|
||||
- What exact software situations cause these vulnerabilities?
|
||||
* Look through CVE database
|
||||
|
||||
## What?
|
||||
* Find out if Rust can help with memory safety within the OS
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue