Can a file end with a 0x80 char? <p>I'm implementing my own version of blowfish encoder/decoder. I use a standard padding of 0x80 if necessary.</p> <p>My question is if I need to add a padding chars even if I don't need it, because in the case of a file that ends naturally with 0x80, in the deconding part I will remove this character, but in this case it is a wrong action, since te 0x80 is part of the file itself. </p> <p>This of course can be solved by adding a final char even if the total number of characters is a multiple of the encoding block (64bit in this case). I can implement this countermeasure, but first I'd prefer to know if I really need it.</p> <p>Natural consequence is thinking if this type of char is chosen because never happens in a file (so the wrong situation above never happens), but I'm not sure at all.</p> <p>Thanks! and sorry for the dummy question..</p>