From nobody Wed Dec 18 09:22:00 2024 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YCp9K3wJMz5h5XL for ; Wed, 18 Dec 2024 09:22:13 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YCp9J4z4Gz4ntP; Wed, 18 Dec 2024 09:22:11 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (124-18-43-234.area1a.commufa.jp [124.18.43.234]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 4BI9M0Rw016942; Wed, 18 Dec 2024 18:22:01 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1734513722; bh=Q18QUMqz7xOI9oJfM4IrtkdooygrV5UnE53X8xyIZrM=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Ou/BWY9Aip2TiacPcQr0JK73pZEHviGdbev3L+gk6+gOzdIDg0y8KgHbHiZDqjUaZ QzhI1ilo/P9Ea5MytV5P6AZAnLHZfnI0mtQ/9esmqt9uyqqjoAH2c596iU2lUTCclI Y0KEA4Uz+ro/9wZLFrsUQavInDkUTf0Lan4EfC+Q= Date: Wed, 18 Dec 2024 18:22:00 +0900 From: Tomoaki AOKI To: Kyle Evans Cc: freebsd-arch@freebsd.org Subject: Re: Removing shar(1) Message-Id: <20241218182200.0096ef17f7a0714291da1afc@dec.sakura.ne.jp> In-Reply-To: <0d63a94d-2773-4efd-b789-0b753ab38b91@FreeBSD.org> References: <0d63a94d-2773-4efd-b789-0b753ab38b91@FreeBSD.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.1) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4YCp9J4z4Gz4ntP X-Spamd-Bar: ---- On Tue, 17 Dec 2024 20:27:16 -0600 Kyle Evans wrote: > Hi, > > I was reminded the other day that shar(1) exists, though it's use is no > longer recommended in ports. The same functionality can be found in > tar(1) instead, so I think we should deorbit /usr/bin/shar and stop > promoting it entirely. sh(1) archives are really problematic from a > user standpoint for at least one reason best explained by the manpage: > > It is easy to insert trojan horses into shar files. It is strongly > recommended that all shell archive files be examined before running > them through sh(1). Archives produced using this implementation of > shar may be easily examined with the command: > > egrep -av '^[X#]' shar.file > > It's hard to advocate for their use in good conscience, much like it's > hard to advocate curl|sh pipes. > > Review: https://reviews.freebsd.org/D48130 > > Thanks, > > Kyle Evans Unfortunately, there's some reporters (sorry, lost track with examples) providing error outputs and/or patches as shar files. (I myself dislike it, though, and consider them as "nonexistent" unless it is a set of patches and multiple comments "it works" are posted.) If we drop it, such users would complain. But when I really need the contents to look into the problem, I usually request the reporters to re-upload the contents as flat texts or non-executable archives like *.txz. And IIRC, RPMs for Linux binaries containing install-time scripts would have similar problems. Regards. -- Tomoaki AOKI