RE: [cobalt-users] Disable FTP Access

["Greg O'Lone" <greg@xxxxxxxxxxxxxxxx>]

> From: cobalt-users-admin@xxxxxxxxxxxxxxx 
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx] On Behalf Of Greg O'Lone
> Sent: Wednesday, April 23, 2003 5:44 PM
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: RE: [cobalt-users] Disable FTP Access
> 
> 
> > -----Original Message-----
> > From: cobalt-users-admin@xxxxxxxxxxxxxxx 
> > [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx] On Behalf Of Ian
> > Sent: Wednesday, April 23, 2003 2:41 PM
> > To: cobalt-users@xxxxxxxxxxxxxxx
> > Subject: RE: [cobalt-users] Disable FTP Access
> > 
> > 
> > Me again and still not got it working, huh..
> > 
> > Not just a bad day but a bad week lol.
> > 
> > This is what I was told to put in...
> > 
> > <VirtualHost 10.0.0.1>
> > ServerName "My virtual FTP server"
> > <Limit LOGIN>
> > DenyAll
> > </Limit>
> > .....
> > </VirtualHost>
> > 
> > And that...
> > 
> > >  ServerName
> > > You don't have to restart or rebot or anything, the next 
> > time someone
> > > connects
> > > to proftpd, your new config will be read!
> > 
> > So I ended up with...
> > 
> > <VirtualHost 212.4.208.213>
> > mail.mccabes-online.co.uk "My virtual FTP server"
> > <Limit LOGIN>
> > DenyAll
> > </Limit>
> > .....
> > </VirtualHost>
> > 
> > and tried,
> > 
> > <VirtualHost 212.4.208.213>
> > ServerName "mail.mccabes-online.co.uk"
> > <Limit LOGIN>
> > DenyAll
> > </Limit>
> > .....
> > </VirtualHost>
> > 
> > And the result being I totally remove all FTP access for all 
> > on that IP
> > address......
> > 
> > Yes guys, I am missing something here very obvious and I will 
> > end up being a
> > dobby from Harry Potter waking myself on the head when I find 
> > out what I am
> > doing wrong here.
> > 
> > Any help much appreciated.
> > 
> > Thanks,
> > 
> > Mac
> > 
> 
> Lets try something rather radical here...In your 
> /etc/proftpd.conf file,
> add the following lines BEFORE the <VirtualHost> directives that are
> already there (using the domain you wish to block of course):
> 
> <VirtualHost stretchedout.com>
> <Limit LOGIN>
> DenyAll
> </Limit>
> </VirtualHost>
> 
> Note: These lines MUST BE BEFORE the other directives. If 
> proftpd sees a
> matching IP address first, it'll allow the login to continue.
> 

Responding to myself, you might also want to add all of the ways someone
could potentially login (since they will all resolve to an IP address):

<VirtualHost stretchedout.com,www.stretchedout.com>
<Limit LOGIN>
DenyAll
</Limit>
</VirtualHost>

--
Greg O'Lone, President
Stretched Out Software, Inc
http://www.stretchedout.com