public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Shaun Oliver <shaun_oliver@optusnet.com.au>
To: speakup@braille.uwo.ca
Subject: Re: proftpd problem
Date: Sun, 23 Feb 2003 03:58:24 +1100	[thread overview]
Message-ID: <20030222165824.GA25253@borg> (raw)
In-Reply-To: <Pine.LNX.4.44.0302221129150.449-100000@h14me.yi.org>

here's a copy of my /etc/proftpd.conf file if anyone neds it for
reference.
I ain't sure where to get the libs and binaries from for ls and stuf,
but,
here's what I dod to allow anonymous acess.
*FILE BEGINS*
# This is a basic ProFTPD configuration file (rename it to 
# 'proftpd.conf' for actual use.  It establishes a single server
# and a single anonymous login.  It assumes that you have a user/group
# "nobody" and "ftp" for normal operation and anon.

ServerName			"Debian"
ServerType			standalone
DeferWelcome			off

ShowSymlinks			on
MultilineRFC2228		on
DefaultServer			on
ShowSymlinks			on
AllowOverwrite			on

TimeoutNoTransfer		600
TimeoutStalled			600
TimeoutIdle			1200

DisplayLogin                    welcome.msg
DisplayFirstChdir               .message
LsDefaultOptions                "-l"

DenyFilter			\*.*/

# Uncomment this if you are using NIS or LDAP to retrieve passwords:
#PersistentPasswd		off

# Port 21 is the standard FTP port.
Port				21

# To prevent DoS attacks, set the maximum number of child processes
# to 30.  If you need to allow more than 30 concurrent connections
# at once, simply increase this value.  Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd)
MaxInstances			30

# Set the user and group that the server normally runs at.
User				nobody
Group				nogroup

# Normally, we want files to be overwriteable.
<Directory /*>
  # Umask 022 is a good standard umask to prevent new files and dirs
  # (second parm) from being group and world writable.
  Umask				022  022

  AllowOverwrite		on
</Directory>

# A basic anonymous configuration, no upload directories.

<Anonymous ~ftp>
  User				ftp
  Group				nogroup
  # We want clients to be able to login with "anonymous" as well as "ftp"
  UserAlias			anonymous ftp

  RequireValidShell		off

  # Limit the maximum number of anonymous logins
  MaxClients			10

  # We want 'welcome.msg' displayed at login, and '.message' displayed
  # in each newly chdired directory.
  DisplayLogin			welcome.msg
  DisplayFirstChdir		.message

  # Limit WRITE everywhere in the anonymous chroot
#  <Directory />
#    <Limit WRITE>
#      DenyAll
#    </Limit>
#  </Directory>

  # Uncomment this if you're brave.
   <Directory /pub/incoming>
  #   # Umask 022 is a good standard umask to prevent new files and dirs
  #   # (second parm) from being group and world writable.
  #  Umask				022  022
              <Limit READ WRITE>
              DenyAll
              </Limit>
             <Limit STOR>
              AllowAll
              </Limit>
   </Directory>

</Anonymous>

*FILE ENDS*
hth

-- 
Shaun Oliver


"We're upgrading /dev/null"


EMAIIL: shaun_oliver@optusnet.com.au
ICQ: 76958435
MSN: blindman_2001@hotmail.com
YAHOO: blindman01_2000


  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Igor Gueths
 ` jwantz
   ` Igor Gueths
 ` Alex Snow
   ` Shaun Oliver [this message]
 Igor Gueths

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030222165824.GA25253@borg \
    --to=shaun_oliver@optusnet.com.au \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).