I would strongly recommend not using OS X. You just can't set up a good server environment with OS X.Ĭonsider getting a new machine if you can't virtualize things, and host your FTP site there. Most companies with a lot of Macs are similar. Out of about 600 desktops, 350-400 of them are Macs, so we actually have a majority of Mac users, but we have zero Macs living in the data center. You can't virtualize it and break services up between servers, so you end up with bizarre situations where a machine does 3 unrelated tasks with different security levels. This is one of the reasons running OS X on your servers is just not a great idea. Anyone who runs FTP in production isolates it. If you insisted on using FTP it wouldn't be the end of the world since this machine would be used for NOTHING else. If you had a virtualized environment I'd suggest spinning up a new Linux VM. Personal feelings leaking out: you lack tact.but now that I've read your username, I guess that's to be expected. On a one on one basis, setting a client up to use a different service for deliverables such as webdav, sftp, etc, would be great, but with the amount of clients using ftp for multiple applications it's not going to work.Įnd goal is simple file delivery for clients in a basic, password based security setup, with clients occasionally uploading to our server to deliver files when it isn't large enough to warrant shipping a physical drive to our location from out of state. ![]() The files are much to large for email, and it is not cost, nor time effective to use a cloud based service for delivering the files. Ftp is pretty standard in this industry, despite the archaic nature of the beast. It's primary use is for syncing data to our offsite hdd array, from our main xsan array, with secondary being an ftp server for clients to access large video deliverables. This server has a 3rd open directory replica, xsan mdc replica, and dns replica. Here's what I have in nf # the FTP document for OS X Server usersĬhroot REAL /Volumes/website_hdd/WEB/website_com/FTP/%d/FTPĭespite how I feel, I will step back and reflect on your post. However, when I add the /FTP/ at the end after /%d/ it still just locks them into the root of their home directory. I would like to lock them into an FTP folder inside their directory, so they don't see the user folders (documents, downloads, etc). However, I'm unable to put them into a sub directory inside their user file. I've added some basic chroot rules in the nf, and added the users in ftpchroot. So far I've figured out that the nf, ftpusers, and ftpchroot is definitely not in /etc/, and it's in /Library/Server/FTP/Config.Įach user is just a user in open directory, with their home directory being in the FTP directory of the website. It doesn't need to be mega secure, it's not major critical file stuff, and we really don't anticipate our clients trying to escape jail and check out our other client's work. ![]() I'll need to do multi users, with each user kept in their jail. I'm needing to set up an ftp server on os x mavericks server.
0 Comments
Leave a Reply. |