KingofGamesYami, on 23 June 2015 - 07:27 PM, said:
If I'm reading this correctly, what you want can be done.
You could create a master server which stores the codes. When a computer attempts to log in, it sends the entered password to the master server via rednet. The master server responds with either "true" or "false", depending on whether or not the correct password was sent.
But, anything using rednet is insecure. The most secure thing I ever did over rednet was set up a rolling-code pda lock, where the pda sent a different password each time. Each password was one-time use only, and a new password was generated from the previous via an algorithm. Of course, if they know the algorithm used, it's easy to break.
I don't understand what you mean by "damage report". A computer cannot tell if it's been destroyed, if that's what your thinking.
Although it's somewhat offtopic, I can recommend reading something about token authentication. Only requires hashing:
1. Client sends request to server
2. Server sends random token to client
3. Client generates his own token and hashes it with the entered pw
4. Client sends the hash value of (server token, client token and pw) plus client token raw to server
5. Server can verify by checking, if server token + client token + pw(from db) has an equal hash value
Easier to implement than to actually explain ^^