Slavakion

For kicks, I've decided to dabble in making my own FTP server. I'm using serv-u corporate. I have two questions.

1) What are some basic security measures I should take? I'm running it on port 28 instead of 21, and I set passive ports from 2000-2010 (no clue why, but the website told me to).

2) Will Sygate act up every time an outside machine tries to connect? If so, can I fix that? And will letting people through destroy the practicality of a firewall on that port?

Yeah, I'm another dangerous n00b with an internet connection. Out of my way before I'm h4x0red.

bitrunner

Are you using a router? If not it would be a good idea, give you a little more security. But your have to forward the ports.

If you really want a server, I'd set up a second machine and use it. That way if it does get hacked, you won't have any personal info on it, and you can just wipe it and start over.

Slavakion

Yeah, I have a router. I know it'd be safer to get another machine, but it's on mine for now. Meh.

nospam

I'll second what bitrunner said about using a second machine. i was using my personal computer for a ftp server (for personal use) and found it getting "hit" way too often for my comfort. set up a second machine (old pentium) and used it instead...no worries now if something happens.

skaven

Running on port 28 doesn't really add any security to your system...that's called "security by obscurity". This is the same security model Microsoft uses, and we all see how effective <i>that</i> is. If somebody wants to hack your box, all it takes is a quick port scan to figure out you're running an FTP server on port 28 rather than 21. Just run the server on port 21 and make sure you've got everything covered.

• Disable guest/anonymous accounts, or at a minimum disable uploads.
• Make sure that you've configured your FTP server to treat your FTP directory as a root directory, so that people can't back up the tree and get to your files. On a linux FTP server this is called a "chroot jail".
• Make sure that if you give access to individual people that they pick "good" passwords.
• Keep your system patched (including your FTP server!!) to prevent any known loopholes from getting exploited.

I also recommend running your FTP server on a second machine. For added security, it's trivial to set up an FTP server on a linux machine (most distributions come with an FTP server already installed; you just need to enable it). That and running a web server are great ways to "get into" linux gently without ditching windows completely.

nothingx

While I can't agree more that this kind of security by obscurity is no excuse for real security practices, I disagree with running it on port 21. Even though a hacker could figure you out by running a port scanner, most don't scan the entire 1-65536 possibe port range. Running your server on one of these other non-obvious ports is a sure-fire way to eliminate a good percentage of would be hackers.

No matter how secure your facility is, its always a good practice not to let anyone know you're there.

gariig

Yeah, I think I would pick some crazy port #, like 38972. If someone port scans every port on your box then well, you are hosed. However, most are only going to scan for 1-1024(or whatever the reserved port range is) and then ports that trojans/virii/worms/etc listen to then move on. However, slap that puppy on another box and keep it patched would be the best thing to do.

Slavakion

1) Did it.
2) Did it.
3) Well, my password is good. It's the only one so far.
4) I'm patched up except for SP2, which breaks too many things for me to switch to yet. (bitch at me all you want, I've heard too many bad stories).

It's not even running right now. It's really just a way for me to easily share something with a friend if I chose to.