3 ms·
We're running FTP servers for two use cases: • Embedded. TFTP and regular FTP have reasonable high-quality libraries for all kinds of microcontrollers. HTTP do
by creshal 11y ago
We're running FTP servers for two use cases:
• Embedded. TFTP and regular FTP have reasonable high-quality libraries for all kinds of microcontrollers. HTTP doesn't have a standardized directory browsing mode, and rsync/bt/sftp/… aren't available for those µcs.
• File uploading with easily set up sandboxing and virtual accounts. We could use something else here, but so far it was cheaper to keep FTP running than to set up SFTP that a) doesn't require system-wide accounts (couldn't do that because of username clashes), and b) is sandboxed out of the box without me having to double- and triple-check there's no weird corner case where you can get out. And not-(S)FTP solutions seem to lack good, reliable, easy to use desktop clients. We're dealing with tens of thousands of files and dozens of gigabytes here that need to be shared with non-technical users, and work outside VPNs, so CIFS and most hipster startup crap doesn't really cut it.
I don't think the embedded situation is going to change any time soon, but I'd really appreciate a less painful SFTP solution for the latter case.