/usr/share/doc/libkcapi/html/ch02s02.html is in libkcapi-doc 1.0.3-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Synchronous Symmetric Cipher API</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"><link rel="home" href="index.html" title="Linux Kernel Crypto API User Space Interface Library"><link rel="up" href="Usage.html" title="Chapter 2. Programming Guidelines"><link rel="prev" href="Usage.html" title="Chapter 2. Programming Guidelines"><link rel="next" href="ch02s03.html" title="Asynchronous Symmetric Cipher API"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Synchronous Symmetric Cipher API</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Usage.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Programming Guidelines</th><td width="20%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm55"></a>Synchronous Symmetric Cipher API</h2></div></div></div><p>
Symmetric ciphers can be used in the following different ways:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
One-shot API: The one-shot API performs an encryption operation
with one API call. With that API call, the caller provides the input
data and immediately receives the output from the cipher operation.
</p></li><li class="listitem"><p>
Stream API: With the stream API, the caller can implement independent
calls to send data to the kernel and receive data from the kernel.
Multiple send calls can be inter-mixed with multiple receive calls.
If the kernel buffer is full, the caller of a subsequent send call will
be put to sleep. Conversely, if the buffer is empty, a caller trying
to read data resulting from a cipher operation will be put to sleep.
Sleeping callers will be woken up by the kernel once buffer space
becomes available or data becomes available, respectively. The detached
nature of the sending/receiving operation allows the implementation of
multi-threaded applications where one or more threads send data and one
or more threads receive data. The threads must operate on the same
cipher handle. However, access to that cipher handle does not need to
be serialized when the stream API calls are invoked as the API calls
only read the cipher handle.
</p></li></ul></div><p>
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Usage.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Usage.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Programming Guidelines </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Asynchronous Symmetric Cipher API</td></tr></table></div></body></html>
|