Title is missing a couple of letters, needs editing to fix?
RefControl is a bit primitive, but if it grows up to be as useful as "Request Policy" and "No Script", it'll be very worthwhile. I've added it.
Thanks for mentioning it!
Every phone has a unique IMEI that is broadcast along with the SIM card number. If they've done their homework, then they're tracking the IMEI as well as the SIM card.
But even if one or two people did as you did, it would be meaningless noise in the sea of data.
There are RFCs that cover the transmission of syslog messages in a secure fashion. 5424, 5425, etc.
There are tools that store syslog messages - in plain text - in a secure fashion.
syslog-ng is just one of them.
This post is "old" and nothing more than a group of people reinventing the wheel.
The *only* way to solve tampering with log data is to store it on another machine and hope hackers don't get to that.
If a hacker gains access to a system with log files on it, the best you can do is make the logging tamper-evident. This means that if the hacker modifies the data, in any way, it can be detected. This includes hash recalculation.
Making the system tamper-evident with hashes simply means that all hashes require a secret input and that the input is only ever stored on the system for the next entry. If you know the secret input for hash#0, then you can calculate the secret input for hash#n, but knowing the secret input for hash#n does not tell you what it was for hash#(n-1). Similarly, the secret input for hash#0 is not stored on the system.
"Just think of a computer as hardware you can program." -- Nigel de la Tierre