Home | History | Annotate | Download | only in libtomcrypt

Lines Matching refs:decrypt

147 and store data in a format independent of the platform.  This means if you encrypt with Blowfish on a PPC it should decrypt
183 the key setup, ECB decrypt and encrypt and test vector routines. After that all five chaining mode routines
432 To encrypt or decrypt a block in ECB mode there are these two functions per cipher:
433 \index{Cipher Encrypt} \index{Cipher Decrypt}
443 These two functions will encrypt or decrypt (respectively) a single block of text\footnote{The size of which depends on
528 /* decrypt the block */
529 blowfish_ecb_decrypt(ct, /* decrypt this 8-byte array */
808 to encrypt whole blocks at a time. However, the library will buffer data allowing the user to encrypt or decrypt partial
819 buffer the output which will allow you to encrypt or decrypt partial blocks without delay.
831 accomplish this by buffering the data required to complete a block. This allows you to encrypt or decrypt any size
892 To actually encrypt or decrypt the following routines are provided:
908 In all cases, \textit{len} is the size of the buffer (as number of octets) to encrypt or decrypt. The CTR, OFB and CFB modes are order sensitive but not
911 five of the modes will return {\bf CRYPT\_OK} on success from the encrypt or decrypt functions.
916 To decrypt in either mode, perform the setup like before (recall you have to fetch the IV value you used), and use the decrypt routine on all of the blocks.
999 /* now we want to decrypt so let's use ctr_setiv */
1071 These will encrypt (or decrypt) the plaintext to the ciphertext buffer (or vice versa). The length is specified by \textit{len} in octets but must be a multiple
1116 To encrypt or decrypt data we use the following two functions:
1130 These will encrypt or decrypt a variable length array of bytes using the F8 mode state specified. The length is specified in bytes and does not have to be a multiple
1195 To encrypt or decrypt data in a streaming mode use the following.
1213 You cannot both encrypt or decrypt with the same \textit{eax} context. For bi--directional communication you will need to initialize
1350 To encrypt or decrypt data use the following.
1363 This will encrypt (or decrypt for the latter) a fixed length of data from \textit{pt} to \textit{ct} (vice versa for the latter).
1389 To terminate a decrypt stream and compared the tag you call the following.
1435 Similarly, this will OCB decrypt, and compare the internally computed tag against the tag provided. \textit{res} is set
1519 /* decrypt it */
1644 This will initialize the GCM state with the given key, IV and AAD value then proceed to encrypt or decrypt the message text and store the final
2892 as an encrypt (and decrypt) function.
2911 sober128\_read() as an encrypt (and decrypt) function.
2954 To decrypt you have to do the exact same steps.
3237 given only $N$ and $e$ appears to be intractable only the owner of the private key can decrypt the ciphertext and compute
3360 This function will RSA decrypt \textit{in} of length \textit{inlen} then OAEP de-pad the resulting data and store it in
3544 /* now let's decrypt the encrypted key */
3872 The data is encrypted to the public ECC \textit{key} such that only the holder of the private key can decrypt the payload. To have multiple
3885 This function will decrypt an encrypted payload. The \textit{key} provided must be the private key corresponding to the public key
4105 \mysection{DSA Encrypt and Decrypt}
4106 As of version 1.07, the DSA keys can be used to encrypt and decrypt small payloads. It works similar to the ECC encryption where
4139 This will decrypt the ciphertext \textit{in} of length \textit{inlen}, and store the original payload in \textit{out} of length \textit{outlen}.
4899 will not be able to sign or decrypt messages at all. Suppose $p$ was prime and $q$ was composite this is just a variation of
5406 /** Decrypt a block
5549 @param direction Encrypt or Decrypt direction (0 or 1)
5574 @param direction Encrypt or Decrypt mode (GCM_ENCRYPT or GCM_DECRYPT)
5711 While both encrypt and decrypt accelerators are not required it is suggested as it makes lrw\_setiv() more efficient.