Secure Coding Standard¶

The strongSwan project adheres to the following recommendations and rules recommended by the CERT C Secure Coding Standard:

Preprocessor (PRE)¶

Full Adherence¶

• PRE03-C. Prefer typedefs to defines for encoding types

• PRE04-C. Do not reuse a standard header file name

• PRE06-C. Enclose header files in an inclusion guard

• PRE09-C. Do not replace secure functions with deprecated or obsolescent functions

Partial Adherence¶

• PRE00-C. Prefer inline or static functions to function-like macros

• PRE01-C. Use parentheses within macros around parameter names

• PRE02-C. Macro replacement lists should be parenthesized

Check Adherence¶

• PRE05-C. Understand macro replacement when concatenating tokens or performing stringification

• PRE07-C. Avoid using repeated question marks

• PRE10-C. Wrap multistatement macros in a do-while loop

• PRE11-C. Do not conclude macro definitions with a semicolon

• PRE12-C. Do not define unsafe macros

• PRE30-C. Do not create a universal character name through concatenation

• PRE31-C. Avoid side-effects in arguments to unsafe macros

• PRE32-C. Do not use preprocessor directives inside macro arguments

No Adherence¶

• PRE08-C. Guarantee that header file names are unique

Declarations and Initialization (DCL)¶

Full Adherence¶

• DCL01-C. Do not reuse variable names in subscopes

• DCL02-C. Use visually distinct identifiers

No Adherence¶

• DCL00-C. Const-qualify immutable objects

• DCL03-C. Use a static assertion to test the value of a constant expression

Expressions (EXP)¶

Integers (INT)¶

Floating Point (FLP)¶

Arrays (ARR)¶

Characters and Strings (STR)¶

Memory Management (MEM)¶

Input Output (FIO)¶

Environment (ENV)¶

Signals (SIG)¶

Error Handling (ERR)¶

Application Programming Interfaces (API)¶

Concurrency (CON)¶

Miscellaneous (MSC)¶

POSIX (POS)¶