Cipher pad block corrupted on Gingerbread?

Two points: 1) The toByte() method isn't clear what it's trying to do, but I'll bet it's wrong, as the line int len = hexString.length()/2; is going to give the same result of 3 for strings of length 6 and 7 (say) 2) You can't rely on converting stings to byte arrays without specifying the Charset to use. Different locales and different run machines may have different default Charsets. You should probably use str.

GetBytes("UTF8") in the algorithm.

I'll do some more testing, but Charset seemed to be a problem... :) – svebee Mar 5 at 23:34 Right...it works then on Gingerbread (2.3) but not on Froyo (2.2) and vice-versa. If I remove charset parameter, it works on 2.2 but not on 2.3. – svebee Mar 6 at 20:46 Here is the same problem - what's the solution then? Use some other algorithms?

Stackoverflow. Com/questions/4536241/aes-gingerbread – svebee Mar 7 at 13:32.

It's problem with BouncyCastle (BouncyCastle AES error when upgrading to 1.45). What I have found is that this results in two different values for BC 1.34 vs 1.45. I couldn't find the solution, yet...

NickT says: "is going to give the same result of 3 for strings of length 6 and 7 (say)" I suppose that length of HEX string in that case is always EVEN number (see function appendHex).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.