Home | History | Annotate | Download | only in libtomcrypt

Lines Matching refs:Developer

78 \begin{large}Developer Manual\end{large}
168 directly (\textit{e.g. sha256\_process()}) this descriptor interface allows the developer to customize their
172 that for the PRNG needs within the library (\textit{e.g. making a RSA key}). All the developer has to do
2018 In order to use the CHC system the developer will have to take a few extra steps. First the \textit{chc\_desc} hash
4662 The ASN.1 \textit{flexi} decoder allows the developer to decode arbitrary ASN.1 DER packets (provided they use data types LibTomCrypt supports) without first knowing
4663 the structure of the data. Where der\_decode \_sequence() requires the developer to specify the data types to decode in advance the flexi decoder is entirely
4930 However, when the end user is not on one of these platforms, the application developer must address the issue of finding
5066 When \textbf{IGNORE\_SPEED} has been defined the default optimization flags for CFLAGS will be disabled which allows the developer to specify new
5357 development simple. In most dependent routines all an end developer has to do is register\_XXX() the descriptor and they are set.
5634 The \textit{name} parameter specifies the name of the cipher. This is what a developer would pass to find\_cipher() to find the cipher in the descriptor