Ah, you mean "special" as in "an additional step", rather than "special case". Sorry -- yes, in that sense.
And, of course, with PHP hardwired to do null padding, the other end must conform. On Jul 19, 9:26 am, "Raymond C. Rodgers" <[email protected]> wrote: > Well, I'm not talking security wise, just compatibility wise, nor did I > say that this was Android specific. However, what I did say was that you > do have to do this in order to get PHP-Android encryption working. > Android to PHP encryption with AES will not "just work" without adding > the null padding or some other mutually recognized padding, so I'd say > that yes this is slightly special as I stated before. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
