Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="38d174fd4c8d504c-35d4ddde-4a004a0a-b93c9975-06f95c1b27a8446c7c01fbbe"><ac:parameter ac:name=""> asynchronous-safe</ac:parameter></ac:structured-macro> *asynchronous-safe* \[[GNU Pth|AA. C References#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 below: |
...
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="5599c8b6ac8595b5-76f7ac09-449b47c8-aaceb217-c74fc8a769135640bb9c1c62"><ac:parameter ac:name=""> availability</ac:parameter></ac:structured-macro> *availability* \[[IEEE Std 610.12 1990|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="ddb7cf14e4c54df8-db33b5a0-45b8412d-a551907a-11371a9fe405d7a82bc16a21"><ac:parameter ac:name=""> conforming program</ac:parameter></ac:structured-macro> *conforming* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\] Conforming programs may depend upon nonportable features of a conforming implementation. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e150c2aa13f38d10-20f26159-48a646d9-90c3a6a4-5fb27ce5e970cbbe1f048863"><ac:parameter ac:name=""> exploit</ac:parameter></ac:structured-macro> *exploit* \[[Seacord 05|AA. C References#Seacord 05]\] An exploit is a piece of software or technique that takes advantage of a security vulnerability to violate an explicit or implicit [security policy|BB. Definitions#security policy]. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="be598c811f019ed6-a9dca925-401a41c8-9f56a0c2-46311ad6170e4b2d7859671e"><ac:parameter ac:name=""> faulterror tolerance</ac:parameter></ac:structured-macro> *faulterror tolerance* \[[IEEE Std 610.12 1990|AA. C References#IEEE Std 610.12 1990]\] The ability of a system or component to continue normal operation despite the presence of hardware or software faultserroneous inputs. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e5744e80-580e-475b-a84e-734932d014ed"><ac:parameter ac:name=""> fault tolerance</ac:parameter></ac:structured-macro>
*fault tolerance* \[[IEEE Std 610.12 1990|AA. C References#IEEE Std 610.12 1990]\]
The ability of a system or component to continue normal operation despite the presence of hardware or software faults. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="12352d28-e154-4df2-91da-066e8f7c986f4ddd7e1e-af4a-440d-a511-49dce5e27f44"><ac:parameter ac:name=""> freestanding environment</ac:parameter></ac:structured-macro> *freestanding environment* \[[ISO/IEC 9899-1999|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="db49c89b03a3379c-78212398-4c2a49b8-b97fb9c5-dc6864aab9cc7c4fa0ffe79d"><ac:parameter ac:name=""> hosted environment</ac:parameter></ac:structured-macro> *hosted environment* \[[ISO/IEC 9899-1999|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="2a78ae090ca5282e-1aa65c7d-41cb41d9-98228ff4-c86e22c59276d89f91d4e531"><ac:parameter ac:name=""> implementation</ac:parameter></ac:structured-macro> *implementation* \[[ISO/IEC 9899-1999|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="f145fc5f14f3dad7-40afb782-4418486f-a2e587eb-c7237fb6d2c720e556d1a6e1"><ac:parameter ac:name=""> implementation-defined behavior</ac:parameter></ac:structured-macro> *implementation-defined behavior* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\] Unspecified behavior where each implementation documents how the choice is made. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="d459979f57393f9d-f3a3a8b7-4763444a-a6c7bfcc-d2025d7867f82f0987384ed4"><ac:parameter ac:name=""> locale-specific behavior</ac:parameter></ac:structured-macro> *locale-specific behavior* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\] Behavior that depends on local conventions of nationality, culture, and language that each implementation documents. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="dc40f2ecde068822-babd429e-45d64af1-b55184c4-fa6ff36157f7486fadc59d57"><ac:parameter ac:name=""> lvalue</ac:parameter></ac:structured-macro> *lvalue* \[[ISO/IEC 9899-1999|AA. C References#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". |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="f6655ca443b23a75-310df6cd-43c149e1-9e46a487-b24dc3537749a7a062952e26"><ac:parameter ac:name=""> mitigation</ac:parameter></ac:structured-macro> *mitigation* \[[Seacord 05|AA. C References#Seacord 05]\] Mitigations are methods, techniques, processes, tools, or runtime libraries that can prevent or limit exploits against vulnerabilities. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="315f270510fdf346-b4685575-48a74c55-bc58a6f7-82920652be60d27164846cba"><ac:parameter ac:name=""> reentrant</ac:parameter></ac:structured-macro> *reentrant* \[[Dowd 06|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="41bb0f8aa26dc814-575d458a-4c11429a-be89ae3b-872ea6c5a5a2324fa2a8de6e"><ac:parameter ac:name=""> reliability</ac:parameter></ac:structured-macro> *reliability* \[[IEEE Std 610.12 1990|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="ebe9d3e56e0c1592-e6bbb92e-452d460c-b62bbd30-b6681e08070432eab5fa76df"><ac:parameter ac:name=""> rvalue</ac:parameter></ac:structured-macro> *rvalue* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\] Value of an expression. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="d6f084796e3225d3-f380c746-461c4f31-a1979a2b-5dd98490f73dc67f83bba43c"><ac:parameter ac:name=""> security flaw</ac:parameter></ac:structured-macro> *security flaw* \[[Seacord 05|AA. C References#Seacord 05]\] A security flaw is a software defect that poses a potential security risk. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="f886dccb81ca51b2-f68ffc0c-48d94c3e-ad0aa8fd-2853d190b608b953da4aa289"><ac:parameter ac:name=""> security policy</ac:parameter></ac:structured-macro> *security policy* \[[Internet Society 00|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="370f0262a5123330-6e6e87d7-4a5546fb-964ca2a4-0f4a4215afc9cdc652d1baec"><ac:parameter ac:name=""> sequence point</ac:parameter></ac:structured-macro> *sequence point* C99 \[[ISO/IEC 9899-1999|AA. C References#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. |
...
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="ce0adc2b53292d0b-21789f8b-41df4909-81c192da-05ae94839eee7cdde3994511"><ac:parameter ac:name=""> strictly conforming</ac:parameter></ac:structured-macro> *strictly conforming* \[[ISO/IEC 9899-1999|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="36c2ad2385fcff28-c3eb40e8-41d2445c-898b8669-7447f52fc178dc14628ce5d8"><ac:parameter ac:name=""> undefined behavior</ac:parameter></ac:structured-macro> *undefined behavior* \[[ISO/IEC 9899-1999|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="5cbf4c79ed0489d7-08b1404b-41644667-8b73a2ae-d7546ab3688e4d5342473c59"><ac:parameter ac:name=""> unspecified behavior</ac:parameter></ac:structured-macro> *unspecified behavior* \[[ISO/IEC 9899-1999|AA. C References#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. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="52441c41651cbcc4-84c4f284-41c3427a-8eee9e45-2e031415efd5df63cef0f565"><ac:parameter ac:name=""> validation</ac:parameter></ac:structured-macro> *validation* \[[IEC 61508-4|AA. C References#IEC 61508-4]\] Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="d2e03bd404a1bbe0-f3008403-4d79488c-b7a9bdee-622d140aecb28e5b001753c9"><ac:parameter ac:name=""> verification</ac:parameter></ac:structured-macro> *verification* \[[IEC 61508-4|AA. C References#IEC 61508-4]\] Confirmation by examination and provision of objective evidence that the requirements have been fulfilled. |
Wiki Markup |
---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="046dd2dfbb85a958-4839adeb-4d7d4cfa-80debe40-825b0684d700a867ffd92d55"><ac:parameter ac:name=""> vulnerability</ac:parameter></ac:structured-macro> *vulnerability* \[[Seacord 05|AA. C References#Seacord 05]\] A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy. |