1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>Terminology</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Linux Kernel Crypto API"><link rel="up" href="Intro.html" title="Chapter&#160;1.&#160;Kernel Crypto API Interface Specification"><link rel="prev" href="Intro.html" title="Chapter&#160;1.&#160;Kernel Crypto API Interface Specification"><link rel="next" href="Architecture.html" title="Chapter&#160;2.&#160;Kernel Crypto API Architecture"></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">Terminology</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Intro.html">Prev</a>&#160;</td><th width="60%" align="center">Chapter&#160;1.&#160;Kernel Crypto API Interface Specification</th><td width="20%" align="right">&#160;<a accesskey="n" href="Architecture.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp1094728508"></a>Terminology</h2></div></div></div><p>
2     The transformation implementation is an actual code or interface
3     to hardware which implements a certain transformation with precisely
4     defined behavior.
5    </p><p>
6     The transformation object (TFM) is an instance of a transformation
7     implementation. There can be multiple transformation objects
8     associated with a single transformation implementation. Each of
9     those transformation objects is held by a crypto API consumer or
10     another transformation. Transformation object is allocated when a
11     crypto API consumer requests a transformation implementation.
12     The consumer is then provided with a structure, which contains
13     a transformation object (TFM).
14    </p><p>
15     The structure that contains transformation objects may also be
16     referred to as a "cipher handle". Such a cipher handle is always
17     subject to the following phases that are reflected in the API calls
18     applicable to such a cipher handle:
19    </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Initialization of a cipher handle.</p></li><li class="listitem"><p>Execution of all intended cipher operations applicable
20      for the handle where the cipher handle must be furnished to
21      every API call.</p></li><li class="listitem"><p>Destruction of a cipher handle.</p></li></ol></div><p>
22     When using the initialization API calls, a cipher handle is
23     created and returned to the consumer. Therefore, please refer
24     to all initialization API calls that refer to the data
25     structure type a consumer is expected to receive and subsequently
26     to use. The initialization API calls have all the same naming
27     conventions of crypto_alloc_*.
28    </p><p>
29     The transformation context is private data associated with
30     the transformation object.
31    </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Intro.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="Intro.html">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="Architecture.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter&#160;1.&#160;Kernel Crypto API Interface Specification&#160;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&#160;Chapter&#160;2.&#160;Kernel Crypto API Architecture</td></tr></table></div></body></html>
32