From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: proftpd problem
Date: Fri, 21 Feb 2003 17:10:26 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0302211707530.10400-100000@igueths> (raw)
In-Reply-To: <Pine.LNX.4.44.0302211325590.22442-100000@babel.hpcc.noaa.gov>
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
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` jwantz
` Igor Gueths [this message]
` Alex Snow
` Shaun Oliver
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=Pine.LNX.4.44.0302211707530.10400-100000@igueths \
--to=igueths@attbi.com \
--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).