I'm not sure if this is what you are looking for, but you can set an RP Access Code for each M1. If the access code you enter into RP doesn't match, then RP won't be able to connect to the M1.
But the RP Access Code doesn't prevent RP from loading the information stored in the database file into RP. So someone could run RP and see all the configuration information, although they couldn't connect to the M1 and change anything in the panel itself.
If you want to protect the database file, you could encrypt it outside of RP.
Assign a password to the entire RP DB and then export the DB out as you see fit.
Modifying the RP code only prevents connection with any other machine that doesn't have the RP code and I really wouldn't suggest...unless you're absolutely sure to notate this in a very safe location as loss of this will prevent any connection.
RP can also be password protected based on user role.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.