This really isn't a very hard problem to solve.
The RC and the OS can share a secret and use a checksum
for packet authentication.
The field control system can use public key methods, so that
a secret need not be globally shared for packet authentication.
Encryption is not required and it is best that the field control
system can see the traffic in any event.
In my view, it would be a nice if FIRST used sound methods
make sure that the communications for the field control system
is not spoofed. Putting the methods out for public review
is the best way to make sure that the chosen means is sound.
I will add that setting up the C and C++ environment as an
open source development environment is the cat's meow for
the FIRST community. A applaud this loudly!
Eugene
Quote:
Originally Posted by Justin
Hi Everyone,
Knowing the FIRST community as I do I'm afraid this post might ruffle some feathers. However in the whole of this conversation, or in an of the documents, I haven't seen any talk of the security employed on the WiFi network that team's robots will now rely on. Is there any encryption whether it be WPA or proprietary from NI? Please note that I am NOT advocating anything malicious during a match but I can think of ways that the WiFi/ethernet/IP(?) nature of the control system could be exploited. Now I recognize that those in FIRST practice gracious professionalism and I would not presume to suggest that anyone involved with FIRST would attempt an exploit. However as we are all reminded to often not everyone in the world lives by the FIRST creed. I think a little prudence would be the responsible course for FIRST and NI in this case.
Can anyone speak to this?
Thanks,
Justin
P.S. I see the post a few posts up now and that is disturbing. Clearly this will have to be addressed, with respects to my thread any ideas what shape such security might likely take?
|