From nobody  Sun Aug 10 11:15:53 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA04029;
          Sun, 10 Aug 1997 11:15:53 -0700 (PDT)
Message-Id: <199708101815.LAA04029@hub.freebsd.org>
Date: Sun, 10 Aug 1997 11:15:53 -0700 (PDT)
From: jgrosch@MooseRiver.com
To: freebsd-gnats-submit@freebsd.org
Subject: mftp get a Segmentation fault
X-Send-Pr-Version: www-1.0

>Number:         4264
>Category:       ports
>Synopsis:       mftp get a Segmentation fault
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Aug 10 11:20:00 PDT 1997
>Closed-Date:    Fri Dec 11 17:50:36 PST 1998
>Last-Modified:  Fri Dec 11 17:52:52 PST 1998
>Originator:     Josef Grosch
>Release:        2.2.2-Stable
>Organization:
Moose River Systems
>Environment:
FreeBSD superior.mooseriver.com 2.2-STABLE FreeBSD 2.2-STABLE #0: Fri Aug  8 00:08:14 PDT 1997     root@superior.mooseriver.com:/usr3/src/sys/compile/PICKLE  i386

>Description:
mftp gets a Segmentation fault when trying to write to a 
directory that the user does not have write permissions
>How-To-Repeat:
as root create a directory, /usr/tmp/foo. The permissions will 
be 0755. As a user, not root, using mftp connect to any 
anonymous ftp site, say ftp.freebsd.org. in mftp change local 
directory to /usr/tmp/foo. Then attempt to get a file such 
as /pub/XFree86/3.3/README. This will cause mftp to terminate 
with a segmentation fault.
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: fenner 
State-Changed-When: Wed Jan 21 16:04:06 PST 1998 
State-Changed-Why:  
No port in the FreeBSD ports system appears to install a program named 
mftp.  What port are you talking about? 

Thanks, 
Bill 
State-Changed-From-To: feedback->closed 
State-Changed-By: steve 
State-Changed-When: Fri Jul 10 17:19:16 PDT 1998 
State-Changed-Why:  
This has been around for a long time and I still don't think 
anyone has figured out what port installs 'mftp'.  I you could 
enlighten us I would be happy to take a look into fixing it for 
you.  Thanks. 

From: Donald Burr <dburr@POBoxes.com>
To: Steve Price <steve@freebsd.org>, freebsd-gnats-submit@freebsd.org
Cc: freebsd-ports@freebsd.org, jgrosch@MooseRiver.com
Subject: Re: ports/4264
Date: Sat, 11 Jul 1998 00:04:48 -0700 (PDT)

 My secret spy satellite informs me that on 11-Jul-98, Steve Price wrote:
 > Synopsis: mftp get a Segmentation fault
 > 
 > State-Changed-From-To: feedback->closed
 > State-Changed-By: steve
 > State-Changed-When: Fri Jul 10 17:19:16 PDT 1998
 > State-Changed-Why: 
 > This has been around for a long time and I still don't think
 > anyone has figured out what port installs 'mftp'.  I you could
 > enlighten us I would be happy to take a look into fixing it for
 > you.  Thanks.
 
 Found it.  It's ${PORTSDIR}/net/moxftp.
 
 This isn't immediately obvious (i.e. a grep of /usr/ports won't find it)
 because the PLIST is generated on-the-fly.
 ---
 Donald Burr <dburr@POBoxes.com> - Ask me for my PGP key | PGP: Your
 WWW HomePage: http://DonaldBurr.base.org/  ICQ #1347455 | right to
 Address: P.O. Box 91212, Santa Barbara, CA 93190-1212   | 'Net privacy.
 Phone: (805) 957-9666    FAX: (800) 492-5954            | USE IT.
 -----------------------------------------------------------------------
   FreeBSD - Turning PCs into Workstations - http://www.freebsd.org/
    (NOTE: POBoxes.com appears to be working again -- fire away!)
State-Changed-From-To: closed->open 
State-Changed-By: steve 
State-Changed-When: Sat Jul 11 10:37:37 PDT 1998 
State-Changed-Why:  
Donald Burr's detective work found out that mftp comes from 
the moxftp port.  Anyone out there with Motif that can test 
and/or fix this problem? 
State-Changed-From-To: open->closed 
State-Changed-By: jseger 
State-Changed-When: Fri Dec 11 17:50:36 PST 1998 
State-Changed-Why:  
This is a bug with moxftp and not the freebsd port of it.  Unless you submit 
patches to fix it, it is not likely to happen.  This port doesn't even 
presently have a MAINTAINER. 
>Unformatted:
