I've been working with Matt to develop the ability for users to protect (and/or encrypt) their macros for a particular hardware key or a group of keys. He just sent me an update for Version 10 that has a new command: /KEYOK
Here's the syntax: /KEYOK,ID1,ID2,,,,; where ID's are the hex identifiers for hardware keys that will be allowed to run the macro. Now...the macro can be encrypted using the /ENCRYPT2 command and only the ID's that are listed in the /KEYOK command will be allowed to run the macro.
Here's some samples:
/KEYLOK,AE1,AE2,AE3,AE4,AE5,AD,148; (only ID's in list can run macro -- put the command at the top of the macro)
With this example, a string variable can be used to pass an identifier to the /KEYOK command. The value of the string could be read from a file, etc...
This new command offers a lot of flexibility to anyone that writes macros that they want to protect.