public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* proftpd problem
@  Igor Gueths
   ` jwantz
   ` Alex Snow
  0 siblings, 2 replies; 6+ messages in thread
From: Igor Gueths @  UTC (permalink / raw)
  To: speakup

Hi all. I am currently using proftpd-1.2.6rc2. I am having problems when
attempting to designate incoming as an upload directory. Even when I chmod
777 /home/ftp/incoming and chown -R ftp /home/ftp, I still get a
permission denied message when trying to upload anything. This even occurs
when I try writing to my own home directory (/home/igueths). In the past,
this used to work when I had anonymous access enabled. However, when I
comment out all the anonymous directives in proftpd.conf, this method no
longer works. Could upgrading to proftpd 1.41 fix this problem? Note
however that I can download from any directory under /home/ftp just fine.
Anyone have any ideas on this one? Thanks!

May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.



^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: proftpd problem
   proftpd problem Igor Gueths
@  ` jwantz
     ` Igor Gueths
   ` Alex Snow
  1 sibling, 1 reply; 6+ messages in thread
From: jwantz @  UTC (permalink / raw)
  To: speakup

Hi Igor, have you checked your current valid chroot within proftpd?  If 
it is set to a directory lower than incoming you definitely won't get 
anywhere!

     Jim Wantz WB0TFK
On Fri, 21 Feb 2003, Igor Gueths wrote:

> Hi all. I am currently using proftpd-1.2.6rc2. I am having problems when
> attempting to designate incoming as an upload directory. Even when I chmod
> 777 /home/ftp/incoming and chown -R ftp /home/ftp, I still get a
> permission denied message when trying to upload anything. This even occurs
> when I try writing to my own home directory (/home/igueths). In the past,
> this used to work when I had anonymous access enabled. However, when I
> comment out all the anonymous directives in proftpd.conf, this method no
> longer works. Could upgrading to proftpd 1.41 fix this problem? Note
> however that I can download from any directory under /home/ftp just fine.
> Anyone have any ideas on this one? Thanks!
> 
> May you code in the power of the source,
> may the kernel, libraries, and utilities be with you,
> throughout all distributions until the end of the epoch.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: proftpd problem
   ` jwantz
@    ` Igor Gueths
  0 siblings, 0 replies; 6+ messages in thread
From: Igor Gueths @  UTC (permalink / raw)
  To: speakup

There are actually no chroot directives in proftpd.conf, none that I could
find anyway. Are there any chroot directives that I don't know about that
can be set in proftpd.conf? Bc the way I want to have it and the way I
have it is have permissions controled by the system. For example, have
system users be able to log into their homedirs and be able to write to
them. This is the way I had it, until I tried disabling anonymous logins.

May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.

On Fri, 21 Feb 2003 jwantz@hpcc.noaa.gov wrote:

> Hi Igor, have you checked your current valid chroot within proftpd?  If
> it is set to a directory lower than incoming you definitely won't get
> anywhere!
>
>      Jim Wantz WB0TFK
> On Fri, 21 Feb 2003, Igor Gueths wrote:
>
> > Hi all. I am currently using proftpd-1.2.6rc2. I am having problems when
> > attempting to designate incoming as an upload directory. Even when I chmod
> > 777 /home/ftp/incoming and chown -R ftp /home/ftp, I still get a
> > permission denied message when trying to upload anything. This even occurs
> > when I try writing to my own home directory (/home/igueths). In the past,
> > this used to work when I had anonymous access enabled. However, when I
> > comment out all the anonymous directives in proftpd.conf, this method no
> > longer works. Could upgrading to proftpd 1.41 fix this problem? Note
> > however that I can download from any directory under /home/ftp just fine.
> > Anyone have any ideas on this one? Thanks!
> >
> > May you code in the power of the source,
> > may the kernel, libraries, and utilities be with you,
> > throughout all distributions until the end of the epoch.
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: proftpd problem
   proftpd problem Igor Gueths
   ` jwantz
@  ` Alex Snow
     ` Shaun Oliver
  1 sibling, 1 reply; 6+ messages in thread
From: Alex Snow @  UTC (permalink / raw)
  To: speakup

That's wierd.  it was doing that for a while with me but I did something
and it worked.  try chgrp users /home/ftp

--
A message from the system administrator: "I've upped my priority, now up yours!"
On Fri, 21 Feb 2003, Igor Gueths wrote:

> Hi all. I am currently using proftpd-1.2.6rc2. I am having problems when
> attempting to designate incoming as an upload directory. Even when I chmod
> 777 /home/ftp/incoming and chown -R ftp /home/ftp, I still get a
> permission denied message when trying to upload anything. This even occurs
> when I try writing to my own home directory (/home/igueths). In the past,
> this used to work when I had anonymous access enabled. However, when I
> comment out all the anonymous directives in proftpd.conf, this method no
> longer works. Could upgrading to proftpd 1.41 fix this problem? Note
> however that I can download from any directory under /home/ftp just fine.
> Anyone have any ideas on this one? Thanks!
>
> May you code in the power of the source,
> may the kernel, libraries, and utilities be with you,
> throughout all distributions until the end of the epoch.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: proftpd problem
   ` Alex Snow
@    ` Shaun Oliver
  0 siblings, 0 replies; 6+ messages in thread
From: Shaun Oliver @  UTC (permalink / raw)
  To: speakup

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


^ permalink raw reply	[flat|nested] 6+ messages in thread
* proftpd problem
@  Igor Gueths
  0 siblings, 0 replies; 6+ messages in thread
From: Igor Gueths @  UTC (permalink / raw)
  To: speakup

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all. I have noticed that only certain machines can access my 
protected ftp server. My machine can't connect to lava-net.com, I get a 
"connection refused message." This also happens when I connect from a 
Linux machine on charter.com. The only other machine that has been able 
to connect successfully besides localhost here, is another Linux box on 
astound.net. My server is currently running in standalone mode, so no 
hosts.allow/hosts.deny to speak of. Does proftpd maintain some sort of 
internal database of banned IP addresses? Anyone have any ideas as to 
why this might suddenly start happening? Thanks!
- -- 
Failure is not an option, it comes bundled with your Microsoft product.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAfBGNNohoaf1zXJMRAkkZAKC5S612hQn3gorLng3Z5VKwCufdqACfdBAC
JfeZRhHO+KyB4a7+7831t9A=
=xAoY
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 6+ messages in thread
end of thread, other threads:[~ UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 proftpd problem Igor Gueths
 ` jwantz
   ` Igor Gueths
 ` Alex Snow
   ` Shaun Oliver
 Igor Gueths

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).