psalad wrote:
Are there any big security issues with running my own ftp server?
Yes. If you run conventional FTP it doesn't encrypt passwords, so before long someone will steal your password and you'll be serving a lot more than the files you think you are. It also may not work depending on how your network is set up. The FTP protocol was designed before it occurred to many people to do network address translation (NAT), so it may not work through NAT even if you're clever in setting it up.
AFP directly to your machine would generally work better and be more secure than FTP, assuming your collaborator also has a Mac. It would, however, be slower in navigating files and folders (file transfers are no faster or slower than FTP).
If you can get data directly between your two machines, rsync through ssh would be a pretty secure solution if set up correctly.
A case can be made for storing a copy of the data away from both work machines, or for working from your machine. With a third location, neither party is likely to overwrite the other's changes while you're trying to use the file. It also gives you some additional degree of backup. On the other hand, there is the problem that you may both, simultaneously, make changes to the same file and upload it, overwriting the other person's changes if your synchronization tool isn't clever enough to realize you've both made changes.
Source code repositories like Subversion, Git, or many others, have pretty much solved this problem for text files. These tools are also often irritating for non-programmers to use. I haven't kept up with systems for managing ungainly, undiffable, binary files or when you really
don't want to keep lots of revisions: you don't probably care much about versions, just about conflicts, so you don't clobber your collaborator's changes.
- Anonymous
Login
Register
FAQ
Search
