From owner-freebsd-questions Sat Sep 8 4:37:18 2001 Delivered-To: freebsd-questions@freebsd.org Received: from topaz.mdcc.cx (topaz.mdcc.cx [212.204.230.141]) by hub.freebsd.org (Postfix) with ESMTP id B267537B406 for ; Sat, 8 Sep 2001 04:37:14 -0700 (PDT) Received: from k7.mavetju.org (topaz.mdcc.cx [212.204.230.141]) by topaz.mdcc.cx (Postfix) with ESMTP id 4B86C2B68C; Sat, 8 Sep 2001 13:37:10 +0200 (CEST) Received: by k7.mavetju.org (Postfix, from userid 1001) id 8387A2AC; Sat, 8 Sep 2001 21:36:04 +1000 (EST) Date: Sat, 8 Sep 2001 21:36:04 +1000 From: Edwin Groothuis To: "R. Lahaye" Cc: FreeBSD Subject: Re: minicom is forbidden ? Message-ID: <20010908213604.A898@k7.mavetju.org> Mail-Followup-To: Edwin Groothuis , "R. Lahaye" , FreeBSD References: <3B99EA04.AE75CCD1@users.sourceforge.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B99EA04.AE75CCD1@users.sourceforge.net>; from lahaye@users.sourceforge.net on Sat, Sep 08, 2001 at 06:51:00PM +0900 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 08, 2001 at 06:51:00PM +0900, R. Lahaye wrote: > When I do a make in /usr/ports/comms/minicom, I get: > ===> minicom-1.83.1_2 is forbidden: Local exploit yielding setuid uucp. That warns you for a possible security problem with minicom. Of course, now that you know it you might not want to install it anymore. Buuuut... if you say "I don't care", get rid of the FORBIDDEN line in the Makefile and install it. > If minicom isn't available, what would be an alternative for setting > up a terminal that listens to the serial port ? kermit Edwin -- Edwin Groothuis | Personal website: http://www.MavEtJu.org edwin@mavetju.org | Interested in MUDs? Visit Fatal Dimensions: ------------------+ http://www.FatalDimensions.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message