From owner-freebsd-standards@FreeBSD.ORG Sat Apr 4 12:50:04 2009 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D73C1065670 for ; Sat, 4 Apr 2009 12:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8CA7F8FC0A for ; Sat, 4 Apr 2009 12:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n34Co4L7028407 for ; Sat, 4 Apr 2009 12:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n34Co4Ej028406; Sat, 4 Apr 2009 12:50:04 GMT (envelope-from gnats) Date: Sat, 4 Apr 2009 12:50:04 GMT Message-Id: <200904041250.n34Co4Ej028406@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Jilles Tjoelker Cc: Subject: Re: bin/25542: sh(1) null char in quoted string X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jilles Tjoelker List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Apr 2009 12:50:04 -0000 The following reply was made to PR bin/25542; it has been noted by GNATS. From: Jilles Tjoelker To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/25542: sh(1) null char in quoted string Date: Sat, 4 Apr 2009 14:41:43 +0200 Considering that fixing this would be a lot of work and cannot be done completely (for example, argument strings and environment variables cannot contain '\0'), I think it is best to close this. sh(1) is meant to process text, not binary data. Trying to process binary data may or will also cause problems if the locale character set is set to UTF-8. As a clarification, this PR is about '\0' bytes in shell scripts, not about making the echo builtin produce '\0' characters. The latter feature works fine and is good. -- Jilles Tjoelker