Just to make it clear:
* Licenses are stored pretty much as the XML files (same fields) and are loaded/checked from the "Secure NV" on startup
* There is several public keys used to check the license signature, which key is used is dependent of the serial number of the scope. The secret key for the first public key, which is used for all early scope serials, has been leaked by Agilent themselves as a mistake and so it's trivial to generate your own licenses for those scope. That's been common knowledge forever ... it's explained in the original thread somewhere pretty early. Nobody published an easy tool, probably because :
- "why risk it": since it deals with "encryption keys" it might have some legal implications that a fw diff doesn't have
- "why risk agilent fixing the problem": if the problem is not widespread, why bother dedicating resources to fix it thoroughly, their current "work around" works well enough and is safe for all previously issued licenses.
In the worst case, if license code was fixed, attacking the firmware should be possible (despite code signing), but I'm certainly not about to risk bricking a 7k$ piece of test gear ...
Just to make it clear:
(...)
In the worst case, if license code was fixed, attacking the firmware should be possible (despite code signing), but I'm certainly not about to risk bricking a 7k$ piece of test gear ...
Your last sentence pretty much sums up all I went through. Happy ending though.
Is anything actually signed or just strong named or whatever they call it?
Just to make it clear:
* There is several public keys used to check the license signature, which key is used is dependent of the serial number of the scope. The secret key for the first public key, which is used for all early scope serials, has been leaked by Agilent themselves as a mistake and so it's trivial to generate your own licenses for those scope.
I wonder how hard it is to change the serial number....
My warranty is fixed to the serial number. I am never gonna change it.
If you can change it, you can change it back
Hey guys,
I am the first one to try the firmware on my 2000x scope and it worked for me. I took the risk of bricking my scope but well I was rewarded with a fully enabled scope.
I don't have a 3000x so I can't say that but I am sure it works on that too since he tested it himself.
So it is a good news for 2000x and 3000x owners.
which FW version is this modified firmware based on ?
What is going to happen if I flash this new modded one and afterwards I flash brand new FW when Agilent releases it ?
Hey
can you tell me Why is the BW limit only does 20Mhz and don't ask me if I want 100Mhz , Full BW or 20Mhz ?
Ps , Is it software related ? , Ie , can you add that into new version of your file ?
and is that possible to somehow add say in the coupling menu to say put 50 Ohm impidance ? ( I suspect not right ? , becouse ther's no Hw whos support that ... )
thank you
I think that there is no 50ohm input at DSOX2000. DSOX2000 and DSOX3000 have quite different motherboards.
I am the first one to try the firmware on my 2000x scope and it worked for me. I took the risk of bricking my scope but well I was rewarded with a fully enabled scope.
I might have seen it work as well. Just so you know.
Confirmed. Works as expected.
Pretty darn cool. Ill wait till someone releases such a fix for free through. I dont like the idea of having to pay for cracks/hacks.
Does the hacked firmware void the warranty??
Does the hacked firmware void the warranty??
More than likely, however like Jailbreaking or something, if you can get the original firmware back on there before you send it in for servicing theyll probably never know you were ever running a customer firmware.
Pretty darn cool. Ill wait till someone releases such a fix for free through. I dont like the idea of having to pay for cracks/hacks.
Uhm... how much djvinc charges for this firmware? It's really uncool...
Pretty darn cool. Ill wait till someone releases such a fix for free through. I dont like the idea of having to pay for cracks/hacks.
Uhm... how much djvinc charges for this firmware? It's really uncool...
Nevermind, apparently Im not allowed to post the details. PM them for the pricing.
Uhm... how much djvinc charges for this firmware? It's really uncool...
The firmware is an initiative that requires a contribution, for many reasons I can't explain easily on this topic. Happy to tell on PM though.
Well, "contribution" should work like "If you like my work - please donate".
It should be all about pride and accomplishment... Making this kind of hacking for living is just low...
I'm surprised, that people on this forum are willing to pay for this - curious what Dave thinks about it
Uhm... how much djvinc charges for this firmware? It's really uncool...
The firmware is an initiative that requires a contribution, for many reasons I can't explain easily on this topic. Happy to tell on PM though.
Oh come on, the reason is you want the money.
Well, "contribution" should work like "If you like my work - please donate".
It should be all about pride and accomplishment... Making this kind of hacking for living is just low...
I'm surprised, that people on this forum are willing to pay for this - curious what Dave thinks about it
I will of course not allow this forum to be used as a basis to peddle anything potentially illegal, either content or services.
Well, "contribution" should work like "If you like my work - please donate".
It should be all about pride and accomplishment... Making this kind of hacking for living is just low...
I'm surprised, that people on this forum are willing to pay for this - curious what Dave thinks about it
I will of course not allow this forum to be used as a basis to peddle anything potentially illegal, either content or services.
Requiring payment (or not) doesn't affect the legality. Possibly the sentence though.
FYI: djvinc's account and posts have been deleted at his request.
Well, now that that's cleaned up, who can provide us with one of the modified firmwares so we can compare it against the original to see what was changed?
Well, "contribution" should work like "If you like my work - please donate".
It should be all about pride and accomplishment... Making this kind of hacking for living is just low...
I'm surprised, that people on this forum are willing to pay for this - curious what Dave thinks about it
I will of course not allow this forum to be used as a basis to peddle anything potentially illegal, either content or services.
Dave what about the Rigol Hack? Is that legal?
Dave what about the Rigol Hack? Is that legal?
How long is a piece of string?
How far do you want to open the can of worms?
IMO there is a big difference between sending a simple existing serial command down the existing provided interface, and reverse engineering and bypassing an encrypted software feature set.
Argue away...
Dave what about the Rigol Hack? Is that legal?
How long is a piece of string?
How far do you want to open the can of worms?
IMO there is a big difference between sending a simple existing serial command down the existing provided interface, and reverse engineering and bypassing an encrypted software feature set.
Argue away...
Really Dave? Read the first page of Hantek /tekway hack. Extensive reverse engineering was done. You have to by past software by renaming.
Perhaps consider taking down your potentially illegal Rigol hack video in the process
"I dont know" in your own tone
Argument is not my thing, they are all just mind chatter between individuals trying to affirm their own belief.