0

Is it possible for base 64 string generated and serialized to file on a windows machine to be deserialized in another base 64 string on a linux machine that is not equal to the string on windows. Implementation is in java using platform encodings. All other non base 64 strings came out fine.

DynamicObject do = new DynamicObject();
do.setBase64Property("MxSgTy==");
NonDynamicProperty ndp = new NonDynamicProperty();
ndp.setString("SimpleString");

Open a object output stream

ObjectOutputStream oo = new ObjectOutputStream(new FileOutputStream("file.ser"));
oo.writeObject(do);
oo.writeObject(ndp);
// close

On the server side (the linux platform)

ObjectInputStream oi = new ObjectInputStream(new FileInputStream("file.ser"));
Object obj = oi.readObject();
if(obj instanceof NonDynamicProperty){
    NonDynamicProperty ndp = (NonDynamicProperty)obj;
    ndp.getString();// outputs SimpleString
}else{
    DynamicObject do = (DynamicObject)obj;
    do.getBase64Property(); // yields uUsYjdh== for example
}

The base64 string is actually the outcome of encoding an encrypted version of a string property. The code that does this is pretty old a real buggy, but I am challenged with figuring out how deep this bug is. Knowing whether it is possible for any reason to have this string values transformed will greatly aid my understanding and put me a step closer to solving the problem.

Rowland Ogwara
  • 19
  • 5
  • 2
    Instead of asking this question, why don't you show us how you encode and write on Windows and how you read and decode on Unix. What would you gain if we answered "Yes" or "No" to your original question? – JB Nizet Mar 09 '14 at 22:00
  • Edited the question added code snippets. http://stackoverflow.com/questions/22204986/why-encrypted-and-base64-encoded-text-appears-different-on-windows-and-linux – Rowland Ogwara Mar 09 '14 at 22:30
  • Well, something must be wrong in the code of DynamicObject. – JB Nizet Mar 09 '14 at 22:42

0 Answers0