Datsys wrote:
I suppose the first thing I should really ask is where/how do I get the ID and the AES keys to begin with?
The next question is how do I get the PT to work with the script? The limtation on the number of characters is not that important since they would both yeild a very stron password anyway.. What is more worthy of consideration is to make sure that the key can not be easily changed one set or would not be easy to tamper with in its original state.
You don't need the original ID and AES keys to set a static password and/or a programming password. If you choose to use the PT, you won't need to use the script. The converse is not, however, true since the script requires the installation of the PT to operate. BTW, if you haven't carefully read the comments in the script, you should do that. There's lots of excellent information in there about this whole process. It also discusses the bit strength of static modhex passwords.
Just run the PT. In the ID field enter the first 24 characters of your GRC hex password. In the AES Key field enter the next 32 characters of that GRC hex password. Check the Create Static Password (No OTP) box.
Leave the Automatic Navigation stuff blank.
In the Programming Protection area, check the box indicating that you want to create or change the password. Two new fields will open for entry of the new password. Leave the field blank for the existing programming password and type the desired new password into the two places shown. Obviously, don't lose the password or you won't be able to reprogram the YK. Click on Update Settings. That should do it. At least it did for me.
Dick