Home | History | Annotate | Download | only in libtomcrypt

Lines Matching refs:secure

797 encrypted under the same key replay and swap attacks are infeasible.  CTR mode may look simple but it is as secure
825 \item Provably as secure as the block cipher being used under a chosen plaintext attack.
2072 The other hashes such as the SHA-1, SHA-2 (that includes SHA-512, SHA-384 and SHA-256) and TIGER-192 are still considered secure
2424 rate of processing and is potentially very secure. It requires AES to be enabled to function. You do not have to register\_cipher() AES first though
2764 Below is a simple snippet to read 10 bytes from Yarrow. It is important to note that this snippet is {\bf NOT} secure since
2864 \textit{Note:} This PRNG is still secure for most tasks but is no longer recommended. Users
2879 Fortuna is more secure than Yarrow in the sense that attackers who learn parts of the entropy being
2956 \mysection{The Secure RNG}
2957 \index{Secure RNG}
3023 \subsection{The Secure PRNG Interface}
3024 It is possible to access the secure RNG through the PRNG interface, and in turn use it within dependent functions such
3025 as the PK API. This simplifies the cryptosystem on platforms where the secure RNG is fast. The secure PRNG never
4924 \mysection{Secure Pseudo Random Number Generators}