Bug 21994

Summary:	[sysinstall] Config of Anonftp (at install) always creates 'incoming'
Product:	Base System	Reporter:	Garance A Drosehn <gad>
Component:	conf	Assignee:	freebsd-qa (Nobody) <qa>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	gad
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description Garance A Drosehn 2000-10-15 01:30:01 UTC

	During the installation process, one has the option of enabling
	anonymous FTP.  I do want anonymous FTP, but I never want to
	create an 'incoming' (world writable) directory.  In the screen
	for "Anonymous FTP configuration", there is a field called
	"Upload subdirectory" which defaults to "incoming".  I delete
	the word "incoming", leaving a null field.  This seems like a
	logical way to say that I don't want ANY upload directory.
	However, the install process still creates ~ftp/incoming, and
	makes it world-writable.

	I consider this a bug, but maybe it's intentional.

Fix: 

I have not tried to figure out a fix for this yet, but I wanted
	to write the PR while I still remembered it, and right after a
	fairly "up-to-the-minute" install...
How-To-Repeat: 
	Install a system.  (I just installed the most recent 4.1-stable
	release, so maybe this is already fixed in 5.x-current?)
	Note that I started the install by booting off the 4.1-release
	CD-ROM, if that is significant to how this works.

Comment 1 Johan Karlsson freebsd_committer

2002-08-21 21:22:10 UTC

Responsible Changed
From-To: freebsd-bugs->freebsd-qa

Over to sysinstall maintainers.

Comment 2 Ceri Davies freebsd_committer

2005-12-29 23:19:44 UTC

On Sat, Oct 14, 2000 at 04:35:45PM -0400, Garance A Drosehn wrote:

> 	During the installation process, one has the option of enabling
> 	anonymous FTP.  I do want anonymous FTP, but I never want to
> 	create an 'incoming' (world writable) directory.  In the screen
> 	for "Anonymous FTP configuration", there is a field called
> 	"Upload subdirectory" which defaults to "incoming".  I delete
> 	the word "incoming", leaving a null field.  This seems like a
> 	logical way to say that I don't want ANY upload directory.
> 	However, the install process still creates ~ftp/incoming, and
> 	makes it world-writable.

This is still a problem, despite the help text on this screen
suggesting that leaving the field blank is ok.\

Where do you suggest that the FTP user's home directory is set to
instead?  /var/empty perhaps?

Ceri

Comment 3 Ceri Davies 2005-12-30 13:39:46 UTC

On Fri, Dec 30, 2005 at 08:31:59AM -0500, John Baldwin wrote:
> On Thursday 29 December 2005 06:20 pm, Ceri Davies wrote:
> > The following reply was made to PR conf/21994; it has been noted by GNATS.
> >
> > From: Ceri Davies <ceri@FreeBSD.org>
> > To: gad@eclipse.acs.rpi.edu
> > Cc: FreeBSD-gnats-submit@freebsd.org
> > Subject: Re: conf/21994: Config of Anonftp (at install) always creates
> > 'incoming' Date: Thu, 29 Dec 2005 23:19:44 +0000
> >
> >  On Sat, Oct 14, 2000 at 04:35:45PM -0400, Garance A Drosehn wrote:
> >  > 	During the installation process, one has the option of enabling
> >  > 	anonymous FTP.  I do want anonymous FTP, but I never want to
> >  > 	create an 'incoming' (world writable) directory.  In the screen
> >  > 	for "Anonymous FTP configuration", there is a field called
> >  > 	"Upload subdirectory" which defaults to "incoming".  I delete
> >  > 	the word "incoming", leaving a null field.  This seems like a
> >  > 	logical way to say that I don't want ANY upload directory.
> >  > 	However, the install process still creates ~ftp/incoming, and
> >  > 	makes it world-writable.
> >
> >  This is still a problem, despite the help text on this screen
> >  suggesting that leaving the field blank is ok.\
> >
> >  Where do you suggest that the FTP user's home directory is set to
> >  instead?  /var/empty perhaps?
> 
> You don't need to change that directory.  That home directory still needs to 
> exist and is where anon ftp files go.  It just needs to not create the 
> world-writable incoming directory if that field is blank.

Yes, of course.  Thanks.

Ceri

Comment 4 Ceri Davies freebsd_committer

2005-12-30 13:47:37 UTC

State Changed
From-To: open->closed

Thanks to jhb's cluebat wielding, it's apparent that this is fixed - 
confirmed with a recent 7.0 snapshot.