posted on Nov, 13 2010 @ 03:24 AM
reply to post by shiman
Yes, friend - It seems that way - I've been wasting a lot of time looking at this, even though there's not much point looking at the encrypted text..
I've came up with only 2 conclusions :
1. Some text editors output text slightly different.
2. My insurance.aes256 file has been corrupted.
The second point is invalid as I've used the checksum on the file to ensure the data is original and wholesome.
I thought I'd highlight anyway, that it appears as though different editors will output different encrypted text with this file - as in vi/vim will
have the full character set although viewing it through a BBE on a Mac will output "penguins" in ACSII - It also seems that using epsilon extension
language in Ksh outputs differences in the encrypted characters also. Which is just plain strange.
Anyway, I can't get my head around it - maybe someone else here can answer why there are variances - something tells me this file isn't a plain old
encrypted file. And until I can figure it out, there's no point in me trying to decrypt it.
edit on 13-11-2010 by anonymousanonymous because: (no reason given)
edit on 13-11-2010 by anonymousanonymous because: (no