Closed huettenhain closed 4 years ago
Small update on the issue:
I didn't know about jserialize
, but seeing the code makes me think that the initial developper of javaobj
was very inspired by it.
I think I might do a full rewrite of some parts of javaobj
to be closer to the jserialize
implementation.
The code would be easier to comment on some parts and javaobj
would be closer to the specification.
Hey @tcalmant, thanks a lot for looking into this!
You can take a look at the deserialize
branch, it provides a new parsing mechanism ported from
the jdeserialize
project.
It's still a work in progress, and maps are not converted as expected... but the file is parsed.
Hi,
I released version 0.4.0 of python-javaobj
(both on GitHub and PyPI): it should solve your issue if you use the v2
implementation.
Just replace import javaobj
by import javaobj.v2 as javaobj
where necessary.
More information is available in the README file.
I let you close the issue if the new implementation solves it.
Works perfectly, thanks a lot!
As mentioned in #23, I am having a similar problem with a piece of serialized data. The data is from a malware sample in Java that I analyzed a while ago, so I did not write this myself. However, I was able to use jdeserialize to deserialize the data, yielding the result OssePatterned.txt.zip. Note that this file only contains a list of path names and key phrases that the malware will decrypt and load next, there is no malicious code in this file itself.
Using the following code:
I get the following error: