CODEWITHSUNDEEP
datetimestamphex
opc0de
opc0de

Reputation: 11768

DateTime hex format decipher

I am working on a little puzzle. I have some timestamps that I know they are timestamps but can't figure out how they are encoded.

3ebf5b89 means 08-October-2013 hour 8 AM but minute I can't provide neither second 
3ebd5f09 means 09-October-2013 hour 8 AM Unknown minute/second.
3ea15d09 means 11-October-2013 hour 8 AM Unknown minute/second but before half past hour.

Any ideas on the encoding?

The weird part is that the dates seem to become lower values as days pass.

If I convert to decimal and substract the big date from the small date I get a value witch converted in seconds is around the days between two dates with a 5 hour error per day.

LE:

I managed to get more accurate time stamps : 

3ea02d09 - Oct 11th, 2013 at 17:10 (hour:minute)
3ea7ff89 - Oct 12th, 2013 at 14:28
3ea7cf09 - Oct 12th, 2013 at 15:34

Upvotes: 11

Views: 1614

Answers (3)

sitifensys
sitifensys

Reputation: 2034

I've tried to play around with the binary form of your inputs and using the bitwise XOR (the poor man's cipher) operator between the value and the corresponding UNIX timestamp.

This is what I've got so far:

(1381507800 ^ 0x3ea02d09) = 0110110011111 00000001111 11 010 001

(1381584480 ^ 0x3ea7ff89) = 0110110011111 11010110001 11 101 001

(1381588440 ^ 0x3ea7cf09) = 0110110011111 11010010010 11 010 001
  • 16bits + 2bits stay stable.
  • The first 13bits plus the last 3bits (which make 16bits if combined) make me think of some kind of rotate shift left.

Please note that my timezone is UTC+1 and thus my UNIX time stamps may not be exact. It would be great if you can get the corresponding timestamps on your system to push this lead further.

Upvotes: 1

Uours
Uours

Reputation: 2492

I wonder those HEX converted to Decimal has some relation to Unix Epoch time :

Those Hex numbers are translating to some valid Dates though different from what you mentioned those are :

Hex 3ebf5b89 = Decimal 1052728201 = Mon, 12 May 2003 08:30:01 GMT

Hex 3ebd5f09 = Decimal 1052598025 = Sat, 10 May 2003 20:20:25 GMT

Hex 3ea15d09 = Decimal 1050762505 = Sat, 19 Apr 2003 14:28:25 GMT


Hex 3ea02d09 = Decimal 1050684681 = Fri, 18 Apr 2003 16:51:21 GMT

Hex 3ea7ff89 = Decimal 1051197321 = Thu, 24 Apr 2003 15:15:21 GMT

Hex 3ea7cf09 = Decimal 1051184905 = Thu, 24 Apr 2003 11:48:25 GMT

Upvotes: 1

medtec
medtec

Reputation: 19

it seemed that the timestamp uses Pi as its base to calculate the time!?

3ea7ff89 - 12 October Hour 14 Minute 28 3ea7cf09 - 12 October Hour 15 Minute 34

difference: 12416 ~ 66 minutes if we divide it by 60 for 60 seconds per minute an after that we divide it by 66 for the minutes difference we get 3.13535353535 that is realy close to Pi. if we use pi to reverse the formular: Pi*66*60=12440 thats in the error range of the not delivered seconds in your timestamps.

Upvotes: 1

Related Questions