<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="c6724390-63e9-4ef3-b9d7-7a027e919280"><ac:parameter ac:name=""> asynchronous-safe</ac:parameter></ac:structured-macro>
asynchronous-safe [[GNU Pth]]
A function is asynchronous-safe, or asynchronous-signal safe, if it can be called safely and without side effects from within a signal handler context. That is, it must be able to be interrupted at any point and run linearly out of sequence without causing an inconsistent state. It must also function properly when global data might itself be in an inconsistent state. Some asynchronous-safe operations are listed here:
- call the
signal()function to reinstall a signal handler - unconditionally modify a
volatile sig_atomic_tvariable (as modification to this type is atomic) - call the
_Exit()function to immediately terminate program execution - invoke an asynchronous-safe function, as specified by your implementation
Few functions are asynchronous-safe. If a function performs any other operations, it is probably not asynchronous-safe.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="273ebd13-6a1c-4ff4-a8eb-6f5270c9d1d9"><ac:parameter ac:name=""> availability</ac:parameter></ac:structured-macro>
availability [[IEEE Std 610.12 1990]]
The degree to which a system or component is operational and accessible when required for use. Often expressed as a probability.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="847c3a5e-e269-4285-8a28-d2cd4a98a5e1"><ac:parameter ac:name=""> basic exception safety</ac:parameter></ac:structured-macro>
basic exception safety [[Stroustrup 01]], [[Sutter 00]]
The basic exception safety guarantee is a property of an operation such that, if the operation terminates by raising an exception, it preserves program state invariants and prevents resource leaks. See also: exception safety, strong exception safety, no-throw guarantee.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="634ac7ed-f767-4c61-8628-e60e02e33a9e"><ac:parameter ac:name=""> conforming program</ac:parameter></ac:structured-macro>
conforming [[ISO/IEC 9899-1999]]
Conforming programs may depend upon nonportable features of a conforming implementation.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="96e25144-f4bc-478e-bbe6-b568395340ef"><ac:parameter ac:name=""> error tolerance</ac:parameter></ac:structured-macro>
error tolerance [[IEEE Std 610.12 1990]]
The ability of a system or component to continue normal operation despite the presence of erroneous inputs.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="acd6c388-7b80-439c-a8be-e24d6d04d28b"><ac:parameter ac:name=""> exception safety</ac:parameter></ac:structured-macro>
exception safety [[Stroustrup 01]]
An operation on an object is said to be exception safe if that operation leaves the object in a valid state when the operation is terminated by throwing an exception. See also: basic exception safety, strong exception safety, no-throw guarantee.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="3787d651-507b-4c6d-be2c-5de33a15e5e8"><ac:parameter ac:name=""> exploit</ac:parameter></ac:structured-macro>
exploit [[Seacord 05a]]
An exploit is a piece of software or technique that takes advantage of a security vulnerability to violate an explicit or implicit security policy.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="415ed344-010e-483c-a29b-851d662c123c"><ac:parameter ac:name=""> fail safe</ac:parameter></ac:structured-macro>
fail safe [[IEEE Std 610.12 1990]]
Pertaining to a system or component that automatically places itself in a safe operating mode in the event of a failure; for example, a traffic light that reverts to blinking red in all directions when normal operation fails.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="2232b819-7d18-447c-b9e1-9b1875fe4550"><ac:parameter ac:name=""> fail soft</ac:parameter></ac:structured-macro>
fail soft [[IEEE Std 610.12 1990]]
Pertaining to a system or component that continues to provide partial operational capability in the event of certain failures; for example, a traffic light that continues to alternate between red and green if the yellow light fails.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="43eac3b9-74ae-417c-a8b4-17b29cea2e96"><ac:parameter ac:name=""> fault tolerance</ac:parameter></ac:structured-macro>
fault tolerance [[IEEE Std 610.12 1990]]
The ability of a system or component to continue normal operation despite the presence of hardware or software faults.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="594903fb-8f9e-4052-94f4-c38f293672a6"><ac:parameter ac:name=""> freestanding environment</ac:parameter></ac:structured-macro>
freestanding environment [[ISO/IEC 9899-1999]]
An environment in which C program execution may take place without any benefit of an operating system. Program startup might occur at some function other than main(), complex types might not be implemented, and only certain minimal library facilities are guaranteed to be available.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="674bf771-a578-4a8f-afba-9d3961b0f630"><ac:parameter ac:name=""> hosted environment</ac:parameter></ac:structured-macro>
hosted environment [[ISO/IEC 9899-1999]]
An environment that is not freestanding. Program startup occurs at main(), complex types are implemented, and all C standard library facilities are available.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="390bd7b3-8c27-4e2f-998d-ee8c21fd3708"><ac:parameter ac:name=""> implementation</ac:parameter></ac:structured-macro>
implementation [[ISO/IEC 9899-1999]]
Particular set of software, running in a particular translation environment under particular control options, that performs translation of programs for, and supports execution of functions in, a particular execution environment.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="3902705d-7a70-4406-8430-71bacbfd02ee"><ac:parameter ac:name=""> implementation-defined behavior</ac:parameter></ac:structured-macro>
implementation-defined behavior [[ISO/IEC 9899-1999]]
Unspecified behavior where each implementation documents how the choice is made.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="5ea83de9-c472-4677-960a-2c626a81bd5f"><ac:parameter ac:name=""> incomplete type</ac:parameter></ac:structured-macro>
incomplete type [[ISO/IEC 9899-1999]]
An incomplete type is a type that describes an identifier but lacks information needed to determine the size of the identifier.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="c00bb967-1623-4dca-aa73-51fcbf184757"><ac:parameter ac:name=""> locale-specific behavior</ac:parameter></ac:structured-macro>
locale-specific behavior [[ISO/IEC 9899-1999]]
Behavior that depends on local conventions of nationality, culture, and language that each implementation documents.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="56c1b4d3-5d66-4473-bebc-e3d609c86228"><ac:parameter ac:name=""> lvalue</ac:parameter></ac:structured-macro>
lvalue [[ISO/IEC 9899-1999]]
An lvalue is an expression with an object type or an incomplete type other than void. The name "lvalue" comes originally from the assignment expression E1 = E2, in which the left operand E1 is required to be a (modifiable) lvalue. It is perhaps better considered as representing an object "locator value".
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="d28d1c62-9be6-47e2-8ff2-e11793ede7ba"><ac:parameter ac:name=""> mitigation</ac:parameter></ac:structured-macro>
mitigation [[Seacord 05a]]
Mitigations are methods, techniques, processes, tools, or runtime libraries that can prevent or limit exploits against vulnerabilities.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="17ae6753-497c-488a-a87e-9822abf2ac1e"><ac:parameter ac:name=""> no-throw guarantee</ac:parameter></ac:structured-macro>
no-throw guarantee [[Sutter 00]]
The no-throw guarantee is a property of an operation such that it is guaranteed to complete successfully without raising or propagating an exception. See also: exception safety, basic exception safety, strong exception safety.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="edeae9f2-bf3e-4e47-9d11-641a417bc211"><ac:parameter ac:name=""> reentrant</ac:parameter></ac:structured-macro>
reentrant [[Dowd 06]]
A function is reentrant if multiple instances of the same function can run in the same address space concurrently without creating the potential for inconsistent states.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="235e72f6-1e28-4e2c-964c-58d906b4cd56"><ac:parameter ac:name=""> reliability</ac:parameter></ac:structured-macro>
reliability [[IEEE Std 610.12 1990]]
The ability of a system or component to perform its required functions under stated conditions for a specified period of time.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="56975b76-82e2-4c30-a018-9ec90262ff8b"><ac:parameter ac:name=""> robustness</ac:parameter></ac:structured-macro>
robustness [[IEEE Std 610.12 1990]]
The degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="69338575-c7cf-4073-b3d8-0f3c2e1607d8"><ac:parameter ac:name=""> rvalue</ac:parameter></ac:structured-macro>
rvalue [[ISO/IEC 9899-1999]]
Value of an expression.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="772a1197-be8b-41cb-9f54-28041a84a9ab"><ac:parameter ac:name=""> security flaw</ac:parameter></ac:structured-macro>
security flaw [[Seacord 05a]]
A security flaw is a software defect that poses a potential security risk.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="54f6c446-ef7a-433c-886f-f2c1b83c1501"><ac:parameter ac:name=""> security policy</ac:parameter></ac:structured-macro>
security policy [[Internet Society 00]]
A set of rules and practices that specify or regulate how a system or organization provides security services to protect sensitive and critical system resources.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="4d991cc0-643f-445d-ada8-c28387928dd0"><ac:parameter ac:name=""> sequence point</ac:parameter></ac:structured-macro>
sequence point C99 [[ISO/IEC 9899-1999]]
Evaluation of an expression may produce side effects. At specific points in the execution sequence called sequence points, all side effects of previous evaluations have completed, and no side effects of subsequent evaluations have yet taken place.
The following sequence points are defined by C99 [[ISO/IEC 9899-1999]]:
- the call to a function, after the arguments have been evaluated
- the end of the first operand of the following operators: && (logical AND); || (logical OR); ? (conditional); , (comma operator)
- the end of a full declarator
- the end of a full expression: an initializer; the expression in an expression statement (that is, at the semicolon); the controlling expression of a selection statement (if or switch); the controlling expression of a while or do statement; each of the expressions of a for statement; the expression in a return statement
- immediately before a function returns
- after the actions associated with each formatted input/output function conversion specifier
- immediately before and immediately after each call to a comparison function, by a standard searching or sorting function, and between any call to a comparison function and any movement of the objects passed as arguments to that call
Note that not all instances of a comma in C code denote a usage of the comma operator. For example, the comma between arguments in a function call is not a sequence point.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="b349237d-4018-4a0d-b60c-5e73d1602198"><ac:parameter ac:name=""> strictly conforming</ac:parameter></ac:structured-macro>
strictly conforming [[ISO/IEC 9899-1999]]
A strictly conforming program is one that uses only those features of the language and library specified in the international standard. Strictly conforming programs are intended to be maximally portable among conforming implementations and can't, for example, depend upon implementation-defined behavior.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="60a1c12c-190b-4b9d-a02f-7f4fa89d78bf"><ac:parameter ac:name=""> strong exception safety</ac:parameter></ac:structured-macro>
strong exception safety [[Stroustrup 01]], [[Sutter 00]]
The strong exception safety guarantee is a property of an operation such that, in addition to satisfying the basic exception safety guarantee, if the operation terminates by raising an exception it has no observable effects on program state. See also: exception safety, basic exception safety, no-throw guarantee.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="9a9f3f2e-e90e-4370-8e79-3dd1c36084fa"><ac:parameter ac:name=""> undefined behavior</ac:parameter></ac:structured-macro>
undefined behavior [[ISO/IEC 9899-1999]]
Behavior, upon use of a nonportable or erroneous program construct or of erroneous data, for which the standard imposes no requirements. An example of undefined behavior is the behavior on integer overflow.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="5b8e0924-60a3-4913-ad26-3a2979ab00f4"><ac:parameter ac:name=""> unspecified behavior</ac:parameter></ac:structured-macro>
unspecified behavior [[ISO/IEC 9899-1999]]
Behavior where the standard provides two or more possibilities and imposes no further requirements on which is chosen in any instance.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="f4bc1d93-7cf0-4cc1-ab0d-7a2c9464c15a"><ac:parameter ac:name=""> validation</ac:parameter></ac:structured-macro>
validation [[IEC 61508-4]]
Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="661e9d52-de4a-4a80-a6de-8b16126252de"><ac:parameter ac:name=""> verification</ac:parameter></ac:structured-macro>
verification [[IEC 61508-4]]
Confirmation by examination and provision of objective evidence that the requirements have been fulfilled.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="1a10d6d1-3283-46d8-b0f3-b43d9cccbfc8"><ac:parameter ac:name=""> vulnerability</ac:parameter></ac:structured-macro>
vulnerability [[Seacord 05a]]
A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy.