Presently I store the user creds in cleartext in the actual script.
This doesnt allow for the script to update itself, poses a security risk and wont support modern auth methods.
To solve this I'm going to import the secure credential storage method used in the RGS LocBot beta.
This will break current implementations but so will any update,
The proposed storage method will store the user creds in an AES encrpyted file next to the script as well as a "key file" with the AES key to allow mutiple users to use the file.
This relies on the admin keeping the key file secure via security policies, but is infinetley more secure than the current implementation
Presently I store the user creds in cleartext in the actual script. This doesnt allow for the script to update itself, poses a security risk and wont support modern auth methods.
To solve this I'm going to import the secure credential storage method used in the RGS LocBot beta. This will break current implementations but so will any update,
The proposed storage method will store the user creds in an AES encrpyted file next to the script as well as a "key file" with the AES key to allow mutiple users to use the file.
This relies on the admin keeping the key file secure via security policies, but is infinetley more secure than the current implementation