Products > Test Equipment
Sniffing the Rigol's internal I2C bus
<< < (705/899) > >>
hematose:
rmd,

Thank you very much for taking this important step! The fact that you got one key that didn't error suggests that we really do have the private key now.

I'll try and go back to take a look at the 4-character codes for the other scopes.

Looking forward to hearing more!
rmd79:

--- Quote from: hematose on September 12, 2014, 02:18:06 am ---Looking forward to hearing more!

--- End quote ---

Thanks,

I'm still working on this, I have a couple of concerns at the moment.  Those are:

1. Both the PUBKEY and PRIVKEY start with 0x00, which I find odd.  It might be perfectly fine/normal, but I'm not sure yet.  Looks like thats normal based on other posts.

2. The PRIVKEY is 16 characters long, but the web version of Riglol only seems to accept 14-character private keys.  Seems normal, I guess we drop the 0x00 from the beginning of the key.

3. The serial number of my MSO1074Z-S is 14 characters long, the serials of the DS2 series seem to be 13 characters long (going by what I see in the code).

FWIW, I'm working with the rigup-0.4.zip codebase and the riglol that it contains, not the web version.  I'm just noting some issues here that I've come across so far, kind of in the hope that someone can chime in on them and maybe help out a little.

I'm also considering purchasing a license for my scope just to see if I can find the option code and maybe validate that the private key is correct.  The reason I have some concerns is that I can't get Riglol to re-produce this license key:

VZ2RCVM-ZK8ZY4L-_______-_______    (V2MP = 0x9ED6D)

I would have thought that if everything was working correctly, I could run something like:

./rigup riglol DS1ZDxxxxxxxxx V2MP

and then get the same license key as above, however the key that it generates is completely different.

EDIT: I should mention that I've added, what I think may be the private key for the MSO1000Z series into my copy of rigup/riglol, otherwise the above would just error out.

Vtech:
Hi rmd79,

You won't be able to generate the same license key as original rigol key. Key generation algorithm uses seed number (k_offset in riglol code). Riglol code sets this number to 0 but genuine Rigol licenses seems to be using true random numbers. Two valid licenses for the same option and serial number can have totally different value.

Buying license also wouldn't help because Rigol doesn't give option codes. They give you 16 character code that you have to enter on their website along with serial number of your unit and in response you get the license key.

Hope this helps
rmd79:
Hi Vtech,

Thanks for the info :)
rmd79:
Vtech,

I forgot to mention, the reason I was thinking about buying an official license for an option in my scope was because I think I might be able to deduce the option code by running the official key through the rigup "info" command, which I've previously done with the official trial key in my scope.  The info command verified the key as OK and also spat out what looks like a option code (V2MP).

So I was thinking I might be able to get a non-trial option code that way, and maybe work from there.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod