String - enc.Base64 - XML - dec.Base64 - String

Question

Well, I encrypt a string using the Base64 Class from sourceforge.net 'iharder'.
Then I write it to an XML-file.
That's working fine. But if I load the XML-file, parse it and want to decode my base64.encrypted String, the decoder produces only senseless characters... the string is not the same as before :-( ...
what am I doing wrong?
Here are some code snippets:
encoding:
String encryptedPassword = Base64.encodeString(Globals.password);decoding:
String decryptedPassword = Base64.decode(password.getFirstChild().toString()).toString();I hope, someone can help me :-D

Answer 1

You are assuming that
"password.getFirstChild().toString()" returns the
result of your "encryption", aren't you? If I use non-encrypted text instead of a encrypted string, it returns my plain-text password without any problems!
And you are
assuming that the Base64 encode and decode methods
work correctly.Hmmm... I just decoded the password for printing it out on screen before writing the encrypted password to the xml-file:
password (norm): test
password (encrypted): dGVzdA==
password (decrypted): [B@14ed577
corresponding code:
String encryptedPassword = Base64.encodeString(Globals.password);
System.out.println("Passwort (norm): "+Globals.password);
System.out.println("Passwort (encrypted): "+encryptedPassword);
System.out.println("Passwort (decrypted): "+Base64.decode(encryptedPassword));That seems to me, that the decoder doesn't work properly.
But I can't believe that... I chose iharder because it is recommended by many users on java.sun!
If you want to debug something, don't try to debug two
things at once. First test that decode() and encode()
are really inverses. (And what's with that .toString()
at the end of your decoding?) This decode-methode returns byte[]... the .toString()-method should generate a string from that byte[]. I know, it looks freaky :-D
Second, find out whether
that DOM calculation is getting the node you believe
it is getting, instead of some other node.Well, the data -> xml -> data routines work fine, I wrote them using non-encrypted plain text. The encryption-decryption statements were added later.
The xml-file's encoding is UTF-8. That's generated and loaded by DOM. I don't think, that DOM mixes up encodings of its own?!? (-> luis_m)