Lines Matching full:encrypt
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
404 should never use the ECB modes directly to encrypt data. Instead you should use the ECB functions to make a chaining mode,
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
445 the same buffer. For the encrypt function \textit{pt}\footnote{pt stands for plaintext.} is the input and
521 /* encrypt the block */
522 blowfish_ecb_encrypt(pt, /* encrypt this 8-byte array */
644 and tables. The decryption and self--test function pointers of both \textit{encrypt only} descriptors are set to \textbf{NULL} and
647 The \textit{encrypt only} descriptors are useful for applications that only use the encryption function of the cipher. Algorithms such
648 as EAX, PMAC and OMAC only require the encryption function. So far this \textit{encrypt only} functionality has only been implemented for
766 A typical symmetric block cipher can be used in chaining modes to effectively encrypt messages larger than the block
808 to encrypt whole blocks at a time. However, the library will buffer data allowing the user to encrypt or decrypt partial
809 blocks without a delay. When this mode is first setup it will initially encrypt the initial vector as required.
819 buffer the output which will allow you to encrypt or decrypt partial blocks without delay.
830 The CTR, CFB and OFB routines provided allow you to encrypt block sizes that differ from the ciphers block size. They
831 accomplish this by buffering the data required to complete a block. This allows you to encrypt or decrypt any size
878 of the cipher you choose. It is important that the IV be random for each unique message you want to encrypt. The
886 increment then encrypt is also supported. By OR'ing \textbf{LTC\_CTR\_RFC3686} with the CTR \textit{mode} value, ctr\_start() will increment
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
909 chunk sensitive. That is you can encrypt \textit{ABCDEF} in three calls like \textit{AB}, \textit{CD}, \textit{EF} or two like \textit{ABCDE} and \textit{F}
911 five of the modes will return {\bf CRYPT\_OK} on success from the encrypt or decrypt functions.
987 /* somehow fill buffer than encrypt it */
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
1099 against the plaintext to encrypt. F8 mode comes with the additional twist that the counter value is secret, encrypted by a \textit{salt key}. We
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
1156 \mysection{Encrypt and Authenticate Modes}
1163 authentication\footnote{Note that since EAX only requires OMAC and CTR you may use \textit{encrypt only} cipher descriptors with this mode.}.
1195 To encrypt or decrypt data in a streaming mode use the following.
1208 The function \textit{eax\_encrypt} will encrypt the bytes in \textit{pt} of \textit{length} octets, and store the ciphertext in
1213 You cannot both encrypt or decrypt with the same \textit{eax} context. For bi--directional communication you will need to initialize
1273 /* now encrypt data, say in a loop or whatever */
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).
1382 This will terminate an encrypt stream \textit{ocb}. If you have trailing bytes of plaintext that will not complete a block
1383 you can pass them here. This will also encrypt the \textit{ptlen} bytes in \textit{pt} and store them in \textit{ct}. It will also
1420 This will OCB encrypt the message \textit{pt} of length \textit{ptlen}, and store the ciphertext in \textit{ct}. The length \textit{ptlen}
1439 CCM is a NIST proposal for encrypt
1502 /* encrypt 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.
2904 encrypt several messages with the same key, and not re--use the same key material.
2911 sober128\_read() as an encrypt (and decrypt) function.
2914 key it from the output of Fortuna (or Yarrow), and use it to encrypt messages. It is also ideal for
2944 /* encrypt buffer */
3143 rsa\_exptmod() to encrypt it.
3235 A person who wants to encrypt with your public key simply forms an integer (the plaintext) $M$ such that
3299 Normally RSA is used to encrypt short symmetric keys which are then used in block ciphers to encrypt a message.
3316 This function will OAEP pad \textit{in} of length \textit{inlen} bytes, RSA encrypt it, and store the ciphertext
3529 if ((err = rsa_encrypt_key(pt, /* data we wish to encrypt */
3867 As the name implies this function encrypts a (symmetric) key, and is not intended for encrypting long messages directly. It will encrypt the
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
4111 This function will encrypt a small payload with a recipients public DSA key.
4125 This will encrypt the payload in \textit{in} of length \textit{inlen} and store the ciphertext in the output buffer \textit{out}. The
5396 /** Encrypt a block
5549 @param direction Encrypt or Decrypt direction (0 or 1)
5574 @param direction Encrypt or Decrypt mode (GCM_ENCRYPT or GCM_DECRYPT)
5677 These two functions are meant for cases where a user wants to encrypt (in ECB mode no less) an array of blocks. These functions are accessed
5704 The accelerator will only be used to encrypt whole blocks. Partial blocks are always handled in software.
5711 While both encrypt and decrypt accelerators are not required it is suggested as it makes lrw\_setiv() more efficient.
