Lines Matching refs:function

12 …he official API specification). Legacy crypto, X.509, TLS, or any other function which is not call…
21function. This document is concerned with environments where the arguments passed to a PSA Crypto …
60 Vulnerability example: suppose that an RSA signature function works by formatting the data in place…
74function processes the ciphertext incrementally by simultaneously writing the plaintext to the out…
78 If a function both has an input argument and an output argument in shared memory, and processes its…
126 …om the content of the buffer being modified or observed during the execution of the function. (...)
242 * Write a small program that uses a PSA function which copies inputs or outputs.
254 We may either copy buffers on an ad-hoc basis using `memcpy()` in each PSA function, or use a unifi…
316 …ng thing. This would not be the case if we relied on the library's copy function to do the poisoni…
326 …nput buffers, keep a copy of the original and copy it back once the PSA function returns. For outp…
330 …f given random data as input. It is possible (if unlikely) that the PSA function will access the p…
336 > This function is not guaranteed to poison the whole region - it may poison only subregion of [add…
340 …ounding buffer lengths up to the nearest multiple of 8 in the poisoning function, although it's re…
360 * Those buffers that are inputs to a PSA function need to be unpoisoned right up until the function
361 * Those buffers that are outputs from a PSA function need to be unpoisoned straight after the funct…
363 These issues may be solved by creating some kind of test wrapper around every PSA function call tha…
382 … location in a shared buffer is not accessed more than once by a driver function. In this section …
434 1. Set up input and output buffers for a PSA function call.
437 4. Call the PSA function.
440 …each location was accessed exactly twice: once by the program's setup and once by the PSA function.
481 …correctly detect careful-access violations when they occur. To do this, write a test function that:
486 Then, write a careful-access test for this function and ensure that it fails.
523 These seem to be a repeat of the same function, however it is useful to retain two separate functio…
584 … have copying added while keeping the code mostly unmodified. Consider a hypothetical PSA function:
616 … allows copying to be easily disabled by defining alternate macros that function as no-ops. Since …
634 The PSA copying function must then have test hooks implemented as outlined in [Validation of copyin…
640 In order to implement transparent memory poisoning we require a wrapper around all PSA function cal…
642 … create wrapper functions that poison the memory and then `#define` PSA function names to be wrapp…
664 …l PSA functions that allow testing code to be inserted at the start and end of a PSA function call.
678 …it would be best to write a test function that misbehaves and test it with memory poisoning. Speci…
680 * Read its input buffer and after calling the input-buffer-copying function to create a local copy …
681 * Write to its output buffer before and after calling the output-buffer-copying function to copy-ba…
683 Then, we could write a test that uses this function with memory poisoning and ensure that it fails.…