5x8
07-30-2009, 10:28 PM
Good day,
For the last while I've been "playing" with an nice bit of software with a really obnoxious locking mechanism.
And while I've made some inroads, and got it to run, something is triping me up and not passing the serial to the software so some features are disabled.
Let me explain further:
Okay 1st things 1st, Its on Linux.
So you install the software and run the id program which generates a serial based on the physical hard disk identifier.
but encrypted
Then you send this off to the firm and get a key which is generated based on that id.
You install the key, the decrypter then loads the key, reruns the id program and decrypts the key if they still match.
If not it fails and the program wont run.
I've been tinkering and basically renamed the id program knocked out small C app to echo back some stuff it wants when it runs,
This works to a point, ie the program loads but I'm missing something when its up and its not getting some internal serial that it would under normal decryption.
Basically what I would like to ask is am I wasting my time this way?
Would a more sensible method be virtualising? or just spending the time and decrypting the system properly? not sure I have the skillset for the that.
I did however stumble across a few encrypted keys, but without the HD id to match them, I don't really know where to start.
The reason this key method is so annoying is, this software runs on ships, so even if a crew can get it running from backups on a different drive, they still have to get the id to shore and the encrypted key back to the machine, not an easy task when you consider Linux, Iridium phones and the like.
Its just a damn overkill.
The software itself is http://www.olex.no quite a nice bit of software but hardly for the masses :-)
Opinions/Thoughs welcome!
Cheers
5x8
Seems this is not the place to ask anything other than how to run a dongledumper :-(
Cheers
For the last while I've been "playing" with an nice bit of software with a really obnoxious locking mechanism.
And while I've made some inroads, and got it to run, something is triping me up and not passing the serial to the software so some features are disabled.
Let me explain further:
Okay 1st things 1st, Its on Linux.
So you install the software and run the id program which generates a serial based on the physical hard disk identifier.
but encrypted
Then you send this off to the firm and get a key which is generated based on that id.
You install the key, the decrypter then loads the key, reruns the id program and decrypts the key if they still match.
If not it fails and the program wont run.
I've been tinkering and basically renamed the id program knocked out small C app to echo back some stuff it wants when it runs,
This works to a point, ie the program loads but I'm missing something when its up and its not getting some internal serial that it would under normal decryption.
Basically what I would like to ask is am I wasting my time this way?
Would a more sensible method be virtualising? or just spending the time and decrypting the system properly? not sure I have the skillset for the that.
I did however stumble across a few encrypted keys, but without the HD id to match them, I don't really know where to start.
The reason this key method is so annoying is, this software runs on ships, so even if a crew can get it running from backups on a different drive, they still have to get the id to shore and the encrypted key back to the machine, not an easy task when you consider Linux, Iridium phones and the like.
Its just a damn overkill.
The software itself is http://www.olex.no quite a nice bit of software but hardly for the masses :-)
Opinions/Thoughs welcome!
Cheers
5x8
Seems this is not the place to ask anything other than how to run a dongledumper :-(
Cheers