From kyle@stdio.com  Thu Oct  9 18:40:53 1997
Received: from cat.stdio.com (stdio.ebola.stdio.com [204.152.115.221])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA13942
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 9 Oct 1997 18:40:45 -0700 (PDT)
          (envelope-from kyle@stdio.com)
Received: (from root@localhost) by cat.stdio.com (8.8.5/8.6.12) id VAA25996; Thu, 9 Oct 1997 21:47:29 -0400 (EDT)
Message-Id: <199710100147.VAA25996@cat.stdio.com>
Date: Thu, 9 Oct 1997 21:47:29 -0400 (EDT)
From: kyle@stdio.com
Reply-To: kyle@stdio.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: slightly broken bb port...
X-Send-Pr-Version: 3.2

>Number:         4737
>Category:       ports
>Synopsis:       bb port depends on "." being in the path, big security hole.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct  9 18:50:00 PDT 1997
>Closed-Date:    Wed Oct 15 16:00:36 PDT 1997
>Last-Modified:  Wed Oct 15 16:03:40 PDT 1997
>Originator:     Kyle McPeek
>Release:        ports-current
>Organization:
Lexmark International
>Environment:
FreeBSD, all versions using ports-current bb port

	
>Description:

	bb port tries to run 'bbconfig freebsd' but if "." is not on your path
	it will fail.  Port makefile should be changed to "./bbconfig freebsd"

>How-To-Repeat:

	since one should not have "." on one's path this should be easily 
	repeatable

>Fix:
	
	change to "./bbconfig freebsd"

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: max 
State-Changed-When: Wed Oct 15 16:00:36 PDT 1997 
State-Changed-Why:  
The Makefile in ports-current calls bbconfig as: 
${SH} bbconfig freebsd 
So your remark isn't quite right. 

If it doesn't work, then you probably have an old Makefile or an old 
bsd.port.mk that doesn't define ${SH} to /bin/sh. 
>Unformatted:
