From owner-freebsd-bugs Sun Jan 23 11:40: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A7EBD14E52 for ; Sun, 23 Jan 2000 11:40:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA47032; Sun, 23 Jan 2000 11:40:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from aberrant.myip.org (adsl-aberrant.ny.inch.com [216.223.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 5065F14BCC for ; Sun, 23 Jan 2000 11:33:46 -0800 (PST) (envelope-from seth@aberrant.myip.org) Received: (from seth@localhost) by aberrant.myip.org (8.9.3/8.9.3) id OAA03617; Sun, 23 Jan 2000 14:33:45 -0500 (EST) (envelope-from seth) Message-Id: <200001231933.OAA03617@aberrant.myip.org> Date: Sun, 23 Jan 2000 14:33:45 -0500 (EST) From: Seth Reply-To: seth@aberrant.myip.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/16316: Enhancement: allow .fakeid to be a named pipe Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 16316 >Category: bin >Synopsis: Enhancement: allow .fakeid to be a named pipe >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Jan 23 11:40:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: Seth >Release: FreeBSD 3.4-STABLE i386 >Organization: >Environment: 3.4-STABLE as of 1/19/2000. >Description: builtins.c checks to see whether .fakeid is a regular file and won't touch it if it's not. It would be great to use a named pipe here so that random words could be inserted via the following (demo) script: #!/bin/sh fakeid=/home/user/.fakeid rm -f $fakeid mkfifo $fakeid while [ 1 ]; do /usr/games/random 50000 < /usr/share/dict/words | head -1 > $fakeid done >How-To-Repeat: Try making .fakeid a named pipe... doesn't work. >Fix: is the S_ISREG test absolutely necessary? Can we add a check for pipes and allow them? Would this introduce security risks? >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message