Replies: 9 comments
-
|
Here it seems to show both |
Beta Was this translation helpful? Give feedback.
-
|
Hi, did you deserialize the Java object? |
Beta Was this translation helpful? Give feedback.
-
|
I guess the short answer is no. Apologies, I'm not sure I follow. I'll be honest and say that thus far I was avoiding installing |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I see you reference these java bytes here. I have obviously thus far missed that part within the source. |
Beta Was this translation helpful? Give feedback.
-
|
This is why the javaobj-py3 library is used. |
Beta Was this translation helpful? Give feedback.
-
|
Shall continue to dig through - I somehow managed to overlook the use of |
Beta Was this translation helpful? Give feedback.
-
|
Yep, I guess documentation needs to be done |
Beta Was this translation helpful? Give feedback.
-
|
That's brilliant :) Happy to hear. I'll be taking a non-object-oriented approach myself - not that one couldn't do the same with CPP. I'm tempted to read that as |
Beta Was this translation helpful? Give feedback.
-
As an exercise, I'm implementing crypt14 decryption in
C, using your excellent work as my guide.I hit my first hurdle when I realised that the
keyextracted from a personal device turned out to be158 bytes, not the131that your code expects.I took a chance looking at the
hexdump, wondering if there is simply some extra27 bytes.This does in fact appear to be the case - just prepended to the rest of the key.
I have at least partially confirmed this, by pulling out the bytes demarcated in key14.py as:
and manually checking that the
sha256hash of the id salt matches the subsequent hashed id bytes.Do you have any idea what these initial
27 bytesmight be? Have you come across them before?It looks like they can simply be ignored, but I just got to wondering.
Beta Was this translation helpful? Give feedback.
All reactions