This is a heads up for all my friends here, especially you moderator types. Sometime in September, another article by yours truly will appear in Radio World Engineering Extra. This one will cover installing OpenSuSE and using it to set up an FTP server.
Believe it or not, in broadcasting, many new applications have appeared that want the good 'ol File Transfer Protocol. These are mostly automated services – for example, traffic and weather reports – that are received, then automatically inserted for airplay that scheduled time(s).
Anyway. You may get some requests for help from people new to OpenSuSE. Just wanted to let you know.
Thanks for the kind words – and I assure you folks, I’m not going to throw these readers off on you. I’ll try to make time to come in here and help myself.
Looks like it’s going to be a two-parter. I’ve just submitted part 1, which merely sets up a basic FTP server that folks can play with. The 2nd part will harden it.
The most common way that a broadcaster will use FTP is, various clients will upload files – paid programs, commercial material, interviews, and so on. Each of these clients will have his/her own directory. I will create accounts for each of these, but with a twist: instead of having separate /home directories for each of these clients, they’ll have a single blank subdirectory under a “master” FTP account, a user called “ftpadmin.”
(You have no idea how delighted I was to see that Yast->Users And Groups->Add User made this such a breeze.)
In other words, the tree will look kind of like,
Everyone is chroot’d. ftpuser1 and 2 can’t see each other’s files, but ftpadmin will have access to all of the uploaded stuff. ftpadmin, on the other hand, won’t be able to go all over the filesystem. As it should be.
It took a little work with the umask and a couple of other settings, but it appears to be working quite well.