Re: vsftpd
- From: Big Bill <billlab951@xxxxxxxxx>
- Date: Fri, 07 Aug 2009 19:11:01 -0400
Allen Kistler a écrit :
What I observe is that authorized X puts something in his ftp space and gives his login to unknown Z who grabs it. It's becomming a temporary xchange facility. I don't care as long as it doesn't restrict my use of the server, what it begins to do.
Warez? You said this was a "family" server. If you've lost control of who has usernames and passwords, that seems to go beyond just family.
It's rather films taken on the net. And yes it has gone beyond the family.
I'd still say use scp for yourself. There's an AlowedUsers directive in the ssh config. Stop and start vsftpd for everyone else using cron. When you stop vsftpd, make sure to kill all the children, too.
And the server will be unaccessible to those who follow the rules !
ssh/scp also has the benefit that your username and password aren't transmitted in the clear across the Internet. Presumably only you can become root. Even better is to disable password authentication in favor of public keys, which stops brute force attacks on your password. Of course, the security of ssh/scp and vsftpd is a whole other topic.
You're right concerning the protection.
I don't want to flush them all only because of a couple of selfish ones.
I'll keep your advice in mind and try to find a setup that will suit the goods and the bads who come on the server.
Thanks
.
- References:
- vsftpd
- From: Big Bill
- Re: vsftpd
- From: Allen Kistler
- Re: vsftpd
- From: Big Bill
- Re: vsftpd
- From: Allen Kistler
- Re: vsftpd
- From: Big Bill
- Re: vsftpd
- From: Allen Kistler
- vsftpd
- Prev by Date: Re: vsftpd
- Next by Date: Re: vsftpd
- Previous by thread: Re: vsftpd
- Next by thread: Re: vsftpd
- Index(es):
Relevant Pages
|