Quote:
|
I can think of a number of things that will interfer, but I am not going to write about it here.
|
Please do. Chances are, at least one other person is thinking about them, and keeping it a secret only makes it easier for black hats to cause havoc
As for preventing unauthorized downloads, encryption would be the main thing. Another thing that would be useful from a forgetting-to-download-the-new-code view as well would be a feature, say, in a dashboard program that continously checked the version of your code, and initiated a redownload if it didn't send a version or sent the wrong one?
Quote:
|
It's also likely (if not already confirmed) that teams won't be able to use wireless in the pits to interface with their robots. This eliminates the possibility of a dishonest person wirelessly downloading a program to someone else's robot.
|
There's a number of ways this could still happen, however. First of all, one could in theory "spoof" a field control system(since it's all 802.11) and use that to download malicious code(though I haven't tested this). It's also possible to get a malicious version of a file from someone else(for example, I could download WPIlib from source, stick a logic bomb in it, and hand it on a flash drive to an unsuspecting team)