Quote:
Originally Posted by Thomas Clark
The robot itself runs an unprotected FTP server. I really fear someone exploiting this, and I've already demonstrated that this is possible (no, I won't post the code).
|
Yes, but an attacker can only get to the robot through the WPA encryption
Quote:
Originally Posted by Thomas Clark
IMHO, they should either use a password, or, better yet, use encrypted SSH file transfer (SFTP).
|
1) FTP transmits passwords clear-text, so adding a password to normal FTP is pretty pointless.
2) SFTP isn't very common, FTPS (SSL) would be a better option.
Quote:
Originally Posted by Thomas Clark
The compiler doesn't support anything besides Windows, and some of us prefer Linux. The IDE I don't care about (I never use IDEs, just makefiles), but FIRST is limiting users' experiences by limiting who can program and on what operating system. IMHO, they should provide a build of the WPI library and compiler for Linux.
|
1) the build of WPIlib would be the same, as it will be built for the target system
2) Java is already supported for ``Linux''
3) C++ is not out-of-the-box supported on *NIX systems, people have gotten it working. Notable posts I've found are
here, and
here. I haven't tinkered with this, as we used Java this year, and have been pretty busy. Now that we've been knocked out of the competition, I think I'll get this working, and throw together a .deb package.*
4) LabVIEW can be developed on ``Linux'', but you must specially request the Linux version of LabVIEW (no cost for FRC teams). Though the RTM needed to deploy is Windows only.
5) Just be glad that the whole thing is open-source, and not a black-box system like 2008 and earlier.
Quote:
Originally Posted by Thomas Clark
Another this is the library. Although it's obvious that tremendous effort was put into it, I can tell that it was rushed to be finished before the build season started. All I can say is that I hope it's better next year.
|
All I can say is that I hope you file some patches before next year. It's fully BSD-3 licensed, on a public SCM. When free-software sucks, you don't get to gripe about it, you find what you don't like, write a patch, and fix it.
*If anyone has any pointers on getting this working, or has experience with other package formats, PM me.