0
Quote
You can spoof an ID, quite easily. (I think, unless 1.6 removed that?) But even so, adding the necessary security to check would be extensive and unnecessary on both the API and the Client.
Quote
CC 1.6 didn't change that and it's unlikely it'll ever change.
The idea is that what the RedNet API calls an "ID" is actually a modem channel, and users can send / receive using pretty much whatever channel they like by accessing the modem API directly. This means that anyone on your wired network, or in range of your wireless network, can intercept and read a copy of any messages they like (regardless as to where you wanted to send them), and they can send messages out as though they owned a computer with any ID they like (regardless as to whether the computers they have access to have those IDs).
The idea is that what the RedNet API calls an "ID" is actually a modem channel, and users can send / receive using pretty much whatever channel they like by accessing the modem API directly. This means that anyone on your wired network, or in range of your wireless network, can intercept and read a copy of any messages they like (regardless as to where you wanted to send them), and they can send messages out as though they owned a computer with any ID they like (regardless as to whether the computers they have access to have those IDs).
While it IS possible to spoof an id, Computercraft 1.6 added hostnames and protocols. They could be used in some way that prevents a computer from receiving a message from a potentially harmful computer, as you can find which computer id is bound to a specific hostname and as a hostname can only be used ONCE on the same protocol. You could subscribe your computer(s) to a protocol and encourage your friends to do the same. That way, you will always know you're receiving messages to them. Sending private messages is going to be a more diffult task though, I fear.
