Lines Matching refs:blowfish
147 and store data in a format independent of the platform. This means if you encrypt with Blowfish on a PPC it should decrypt
148 on an x86 with zero problems. The consistent API also means that if you learn how to use Blowfish with the library you
425 that you should only used this scheduled key with the intended cipher. For example, if you call \textit{blowfish\_setup()} do not
496 An example snippet that encodes a block with Blowfish in ECB mode.
498 \index{blowfish\_setup()} \index{blowfish\_ecb\_encrypt()} \index{blowfish\_ecb\_decrypt()} \index{blowfish\_done()}
603 \index{blowfish\_desc} \index{xtea\_desc} \index{rc2\_desc} \index{rc5\_desc} \index{rc6\_desc} \index{saferp\_desc} \index{aes\_desc} \index{twofish\_desc}
610 \hline Blowfish & blowfish\_desc & 8 & 8 $\ldots$ 56 & 16 \\
692 the location in the array where the cipher was found. For example, to indirectly setup Blowfish you can also use:
705 printf("Unable to register Blowfish cipher.");
712 cipher_descriptor[find_cipher("blowfish")].
714 printf("Error setting up Blowfish: %s\n", error_to_string(err));
796 Where $W$ is the size of a block in bits (e.g. 64 for Blowfish). As long as the initial vector is random for each message
2214 of the cipher\footnote{The cipher must have a 64 or 128 bit block size. Such as CAST5, Blowfish, DES, AES, Twofish, etc.} you
