# Will using a 32 character key for Blowfish make it a 32 bit encryption?

I am sorry if it sounds naive but I have been searching and searching regarding what kind of encryption we end up with if we use a key of length 32 characters?

This article https://www.embedded.com/design/configurable-systems/4024599/Encrypting-data-with-the-Blowfish-algorithm explains how the algorithm works on the plaintext quite clearly but nowhere do I find the difference a key length will make.

=========Edit==========
An example of key is 996b352b-beb9-5628-a61d-4f0fbb72844e

• Ignoring the differences of [ascii] "characters" and bytes, assuming you meant real bytes. 32 "characters", or 32 bytes is 256-bits. Key size is distinct to the security of the function. I.e. Curve25519 has 256-bit keys with 128-bit security. – cypherfox Apr 18 '18 at 6:59
• If your characters are hex, then $\log_2(16^{32}) = 128$-bit key. – cypherfox Apr 18 '18 at 7:01
• Do you want to amend your title about the 32 bit thing? That's 4 bytes. – Paul Uszak Apr 18 '18 at 23:03
• A character is generally one byte but while a byte has 256 possibilities (8-bits) the number of characters per byte depends on the encoding. Best to start with understanding what A byte and a character is—Google is you find here.. – zaph Apr 18 '18 at 23:03
• @Surefoot The example key is a GUID representation and as such the - characters are just for a nice display. So the underlying value is 32-bytes of hexadecimal representing 128-bits. – zaph Apr 18 '18 at 23:09

Well, it's a kind of marketing speak. If you look through the individual entries of this list of block ciphers, you'll see that they are categorised by two distinct parameters.

1. Block size. This is the number of bits that the cipher operates on at a single time. Blowfish has a 64 bit block.

2. Key size. Unsurprisingly, this is the length of the key.

These two parameters are somewhat independent, but key length >= block width. Blowfish's key can be up to 56 bytes, and all things being equal, the longer the key the higher the security level. Crypto guys tend to refer to bits though rather than bytes.

With reference to your question, I'd pick the longer number when telling someone about how secure my kit is. Otherwise you have to give out two numbers. You could say Blowfish128 if you want to say anything at all.

PS. Not sure if this matters to you, but the designer of Blowfish recommends using Twofish instead.

PPS. Further to some comments you've had, be aware that cryptographers would assume that your key consists of independently and uniformly distributed bytes, rather than text characters. Please do not confuse key with password. An error of understanding here can have very serious consequences for the security of your system. Your example key is actually $\operatorname{log_2}(16) \times 32 = 128$ bits long. Modern crypto really warrants a minimum block width of 128 bits though to prevent various attacks, but that's a call only you can make.

• I believe Schneier, the main designer of Twofish, has stated he now uses AES. – zaph Apr 19 '18 at 21:12
• @zaph It's a shame he's lost confidence in it. Do you know why? – Paul Uszak Apr 19 '18 at 21:23
• I doubt that Bruce has lost confidence in Twofish, I have not seen that stated anywhere. I think it is simple: AES is The Advanced Encryption Standard. Among other things interoperability is a good reason to go with AES and there is now more experience and cryptanalysis on AES. This does not mean Twofish is not secure. – zaph Apr 19 '18 at 21:33
• ^ Plus, there are widely available CPU instructions for computing AES very quickly for relatively little code – Ella Rose Apr 19 '18 at 21:38
• @zaph For what it's worth, he doesn't seem to have even lost confidence in Blowfish (although recommends against it due to the small block size). – forest Apr 25 '18 at 3:48