Searched full:verification (Results 1 – 25 of 75) sorted by relevance
123
| /Documentation/trace/rv/ |
| D | runtime-verification.rst | 2 Runtime Verification
5 Runtime Verification (RV) is a lightweight (yet rigorous) method that
6 complements classical exhaustive verification techniques (such as *model
19 *online* verification of a system, enabling the *reaction* for unexpected
26 A monitor is the central part of the runtime verification of a system. The
30 In Linux terms, the runtime verification monitors are encapsulated inside the
41 | (instrumentation) | | (verification) | | (specification) |
54 In addition to the verification and monitoring of the system, a monitor can
64 For further information about the principles of runtime verification and
67 Bartocci, Ezio, et al. *Introduction to runtime verification.* In: Lectures on
[all …]
|
| D | index.rst | 2 Runtime Verification
9 runtime-verification.rst
|
| D | da_monitor_synthesis.rst | 4 The starting point for the application of runtime verification (RV) techniques
14 In Linux terms, the runtime verification monitors are encapsulated inside
26 | (instrumentation) | | (verification) | | (specification) |
|
| D | monitor_wwnr.rst | 45 Grapviz Dot file in tools/verification/models/wwnr.dot
|
| D | monitor_wip.rst | 55 Grapviz Dot file in tools/verification/models/wip.dot
|
| D | deterministic_automata.rst | 51 In the paper "Efficient formal verification for the Linux kernel",
182 Silva. Efficient formal verification for the Linux kernel. In:
|
| /Documentation/tools/rv/ |
| D | rv.rst | 7 Runtime Verification
20 Runtime Verification (**RV**) is a lightweight (yet rigorous) method argument
21 for formal verification with a practical approach for complex systems.
28 verification (rv) monitors.
|
| D | index.rst | 4 Runtime verification (rv) tool
7 **rv** tool provides the interface for a collection of runtime verification
|
| /Documentation/filesystems/xfs/ |
| D | xfs-self-describing-metadata.rst | 12 scalability, but of verification of the filesystem structure. Scalabilty of the
15 is this very scalability that causes the verification problem.
50 verification of metadata values, looking for values that are in range (and hence
51 not detected by automated verification checks) but are not correct. Finding and
76 self identifying and we can do much more expansive automated verification of the
84 contain, a large amount of the manual verification work can be skipped.
129 present that the run-time verification is not detecting.
156 The verification is completely stateless - it is done independently of the
166 For read verification, the caller needs to specify the expected type of metadata
168 object matches what was expected. If the verification process fails, then it
[all …]
|
| /Documentation/security/ |
| D | digsig.rst | 2 Digital Signature Verification API
19 Digital signature verification API provides a method to verify digital signature.
22 Digital signature verification is implemented using cut-down kernel port of
58 digsig_verify() - digital signature verification with public key
62 * digsig_verify() - digital signature verification with public key
|
| /Documentation/filesystems/ |
| D | btrfs.rst | 24 * Scrub (on-line checksum verification)
33 * Read/write metadata verification
|
| D | fsverity.rst | 100 verification`_. This approach should be used only with great care.
147 if the `Built-in signature verification`_ feature is being used. It
253 fs-verity compatible verification of the file. This only makes sense
287 signature verification`_.
301 implement fs-verity compatible verification anyway (though absent a
358 would circumvent the data verification.
365 opening the file will fail. See `Built-in signature verification`_.
447 Built-in signature verification
451 verification of fs-verity builtin signatures.
455 alternatives (such as userspace signature verification, and IMA
[all …]
|
| /Documentation/crypto/ |
| D | asymmetric-keys.rst | 12 - Signature verification.
112 1) Signature verification.
115 required for verification, but not currently supported, and others
119 Signature Verification
122 An operation is provided to perform cryptographic signature verification, using
225 Optional. This is the entry point for signature verification. The
346 for signature verification.
357 verification.
372 This allows for verification of certificate chains by adding each
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | testing-overview.rst | 102 * 运行时确认（Runtime Verification）支持检查给定子系统的特定行为。参阅
103 Documentation/trace/rv/runtime-verification.rst。
|
| /Documentation/scsi/ |
| D | cxgb3i.rst | 13 as CRC computation and verification, and direct DMA to the final host memory
16 - iSCSI PDU digest generation and verification
|
| /Documentation/driver-api/mei/ |
| D | hdcp.rst | 15 for decryption and verification.
|
| /Documentation/devicetree/bindings/crypto/ |
| D | aspeed,ast2600-acry.yaml | 14 of ECDSA/RSA signature and verification. Basically, ACRY can be
|
| /Documentation/usb/ |
| D | authorization.rst | 66 security verification you can make (or the best, for someone willing
89 verification stuff with PKI, so you don't depend on a shared secret,
|
| /Documentation/devicetree/bindings/soc/microchip/ |
| D | microchip,mpfs-sys-controller.yaml | 15 services include hardware rng, reprogramming of the FPGA and verification of the
|
| /Documentation/networking/ |
| D | generic-hdlc.rst | 114 - t391 - link integrity verification polling timer (in seconds) - user
115 - t392 - polling verification timer (in seconds) - network
|
| /Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 97 verification fails. Use encoding data from the specified device. This
128 since verification of hash blocks is less performance critical than data
136 Verification of roothash depends on the config DM_VERITY_VERIFY_ROOTHASH_SIG
|
| /Documentation/arch/x86/ |
| D | intel_txt.rst | 15 - Measurement and verification of launched environment
87 shutdown, and there is support for policy-based execution/verification.
184 Tboot's policy determines what happens if the verification fails.
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-chromeos-acpi | 151 firmware verification step and the kernel verification step
|
| D | sysfs-fs-incfs | 58 Description: Returns number of reads that failed because of hash verification
|
| /Documentation/driver-api/mmc/ |
| D | mmc-test.rst | 112 To run test number 4 (Basic read with data verification):
141 | | | without data verification. |
146 | | (with data verification) | single 512-Byte block to the MMC card |
147 | | | with data verification by reading back |
151 | | (with data verification) | |
284 [ 1234.567891] mmc0: Test case 4. Basic read (with data verification)...
288 In this example, test case 4 (Basic read with data verification) was executed, and the result was O…
|
123