Yeah I thought it was odd as well.
I've attached some patches of the rigup-0.4 and riglol-20140717 code that I've been modifying. Actually, the patches are not the code I've been working on, since thats a bit of a mess now, they are just the basics that would get anyone else to the same point I'm currently at.
So, with the patches you can use "rigup scan" to scan the MSO1000Z memory dump for the keys and generate the key file. it should find the keys and also the serial number. The riglol patch just adds the private key into riglol and makes riglol recognise the MSO1000Z serial number (which in my case begins with "DS1ZD", and I'm assuming they all do).
If there is someone here who wants to look further into this, I could provide the portion of my scope's memory dump containing the keys (or the whole thing), as well as the key file generated by "rigup scan", the valid license key that my scope accepts and that "rigup info" can verify as OK, and anything else you need. Just PM me via the forum.
The point at where things may have gone wrong could be the code that breaks the public key and solves the private key. I'm thinking that if "rigup info" can decode a valid key using the public key retrieved by "rigup scan", then it would make sense that if the code that calculates the private key is getting it wrong, riglol would not be able to produce a valid key.
I don't know how to go about verifying whether to not thats the case.