RP Access Code....It Doesn't Matter????

[video321]

I don't understand what may be going on here, but no matter what I try to do I can't seem to change the RP access code to where anything actually makes a difference. I change it in RP Acct. Details, save the account, send it, and even resend the XEP, but it doesn't matter as I can still connect using any RP access code I want????

To clarify...I can open RP and before connecting enter absolutely anything for the RP access code, save it or not, then connect and verify over ethernet.

There has to be something I'm completely missing, but I don't see it???

ok...this is interesting. If I copy over a backup of the database, then all of a sudden I must enter the correct RP access code. Any idea why it behaves this way?

 

[thill]

I don't understand what may be going on here, but no matter what I try to do I can't seem to change the RP access code to where anything actually makes a difference. I change it in RP Acct. Details, save the account, send it, and even resend the XEP, but it doesn't matter as I can still connect using any RP access code I want????

To clarify...I can open RP and before connecting enter absolutely anything for the RP access code, save it or not, then connect and verify over ethernet.

There has to be something I'm completely missing, but I don't see it???

ok...this is interesting. If I copy over a backup of the database, then all of a sudden I must enter the correct RP access code. Any idea why it behaves this way?

Found something about this in an old post. Apparently your RP database hides three 3 copies of the RP Access code for each account. Code #1 is the currently displayed code. Code 2 is the last or most recent old code. Code 3 is the code before that. And there's an option that allows alarm companies to globally change their RP code on all accounts, even though the change doesn't take place until RP next connects to the panel(s). On the accounts screen you can change displayed RP code, but when RP tries to connect it can fall back to any of the last 3 codes to get a connection. Upon connection, M1 will store the new code. The safety is that this only works with your copy of the software. Hackers or others could not do this unless they stole your database. So when you copied over your database file you destroyed the saved codes and that prevented you from connecting.

 

[video321]

Ah...you know I did find that old post through a search as well, but didn't read closely enough to think it through as "I can enter anything because the local database has a valid backup code stored." I took it more as it stored codes for the last (3) logins, so I logged in more than 3 times and that's why I wasn't seeing it. I had read it well before I copied over my backup Db and didn't even make the connection :blush:

Thanks for posting...a closer read makes all the difference!

On a side note, I'm realizing that changing the RP code really doesn't buy me anything. For anyone to connect they would also have to know the serial#. The weak link in the whole system are the local and backup databases that store my name, address, and codes! At that point, who needs to connect??? I'll definitely look to encrypt those files.

 

[Del91574]

Rp does encrypt those files and DB information in options>DB security, with the password and all 4 fields that need to be filled in in order for the information to be opened up on another machine. I'm sure if someone really wants to spend all that time and go through the DB files to try to open them....well I think it's a little nuts.

I had to move and synchronize multiple DB's on my laptop(s) and 2 office computers when I migrated from XP machines to new Win7 machines and I had a heck of a time because I couldn't remember the PW's that I had in the DB security on the various machines.