Security check
From ReactOS
| This page is a short article on something that should have a lot more information written on it. If you know anything else about it, you are STRONGLY encouraged to add the information in. If you are unsure of proper formatting or style, add it to the talk page or this page itself as you think best and others will help. |
| This page is a candidate for speedy deletion If you disagree with its speedy deletion, please explain why on its talk page.
Watch also the Criteria for speedy deletion! |
Extending the Continuous Integration System with automatic security checks can help achieve a more stable ReactOS with less bugs.
Please describe any checks you can think of below.
Contents |
Kind of security checks
- Memory.
- Locks.
- System calls.
Memory
- Used for
- Storing of program data during execution of a program.
- Checks
- Allocated memory is released.
- Consequences of incorrect use
- Memory leaks. Memory is not available for other use when not released.
- System crashes.
Locks
- Used for
- Synchronization. Protecting access to shared resources.
- Checks
- Locks are released.
- Consequences of incorrect use
- Race conditions. A set of operations that need to be executed in a specific order to result in the correct outcome was executed in a different order.
- System or application crashes.
System calls
- Used for
- Application access to system resources.
- Checks
- Validate that memory for system call parameters can be accessed.
- Consequences of incorrect use
- System crashes.
Parameters
- Used for
- Controlling program behaviour.
- Checks
- Validate that size of string buffers are specified correctly in WCHARs instead of bytes and vice versa for certain run-time library functions.
- Consequences of incorrect use
- Incorrect program behaviour.[[Category:Security
