static.eightyeight
Member
Looking for some input...
I felt like I needed to make a pseudo account (my other account pretty much is my name) to discuss this topic. We are now receiving a product from an OEM that has decided to "lock" a program to a unique processor serial number.
Here is the overview, the program file pretty much has EVERY routine source locked (encryption 9 V30). Unfortunately, no real good way of following the logic, other than cross referencing tags and seeing what routines they reside in. It would appear that they GSV the processor serial number, then compare it to a hard coded value, and if happy will then call the routines to run the logic.
I'm am all for encrypting proprietary algorithms and logic (AOI's and what not), but locking a program to a specific serial number for a processor to force you to be fully dependent on the OEM, not a fan (very very sneaky). We will be opening discussions with them about this tactic, and they need to explain to us why they feel this is necessary, since there is legal mumbo jumbo that might have them stepping in a grey area.
Has anyone seen / used this tactic before? I totally understand that processor replacement due to failure is extremely RARE, but this just doesn't seem like a good tactic.
I felt like I needed to make a pseudo account (my other account pretty much is my name) to discuss this topic. We are now receiving a product from an OEM that has decided to "lock" a program to a unique processor serial number.
Here is the overview, the program file pretty much has EVERY routine source locked (encryption 9 V30). Unfortunately, no real good way of following the logic, other than cross referencing tags and seeing what routines they reside in. It would appear that they GSV the processor serial number, then compare it to a hard coded value, and if happy will then call the routines to run the logic.
I'm am all for encrypting proprietary algorithms and logic (AOI's and what not), but locking a program to a specific serial number for a processor to force you to be fully dependent on the OEM, not a fan (very very sneaky). We will be opening discussions with them about this tactic, and they need to explain to us why they feel this is necessary, since there is legal mumbo jumbo that might have them stepping in a grey area.
Has anyone seen / used this tactic before? I totally understand that processor replacement due to failure is extremely RARE, but this just doesn't seem like a good tactic.