From nobody Wed Dec 18 02:27:16 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 4YCcyZ39jPz5gb6D
	for <freebsd-arch@mlmmj.nyi.freebsd.org>; Wed, 18 Dec 2024 02:27:18 +0000 (UTC)
	(envelope-from kevans@FreeBSD.org)
Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83])
	(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-signature RSA-PSS (4096 bits) client-digest SHA256)
	(Client CN "smtp.freebsd.org", Issuer "R10" (verified OK))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4YCcyZ2Wd7z4Bsr;
	Wed, 18 Dec 2024 02:27:18 +0000 (UTC)
	(envelope-from kevans@FreeBSD.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim;
	t=1734488838;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding;
	bh=coXwrNHv/e+0jlgofS4brVWkRS1dBgMFKsURi11al/8=;
	b=WPAbiSSDycYPOQoqRxXrFCeZLRJSQ8aJk6RflZoIPikQKLWbYN8gpr3F/2IidacLCu6YKs
	bXvSnlxGN1uMkfpAURFHHBkVmpYSjmQhJ2qcBprpmVChf+sD0seWid+llmlfzMIcSfypgZ
	PFhER77rXYSPlTe+RaOxVYP8eyQ/FNzUsK8EBWUHtRDicAoKzzBDP2aMnz0xYer8SnWmVz
	AotT+PNIdgVOAlo4VbB5QGvdNU+x5WHsGLoiIi+ubvsHCXaDX1IDeXTmE5Bqe4+4en4Oir
	8mXJyP7893+MpnhOdg1gJwy2DWAk6S+qcBVERPIYmUD0tmJ2O0Dv2yL6+3GvwA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org;
	s=dkim; t=1734488838;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding;
	bh=coXwrNHv/e+0jlgofS4brVWkRS1dBgMFKsURi11al/8=;
	b=GvNWl5DDUXp/Ov3DIqO9RFUXnO97TQzbkhPe49VGVkT7GUti0zzyTFlxQc2WUDD3/SPzT1
	ogxFRZZYw+m2ILt6iWUbCckkua3WmwNZLq0XHx3n/muHY20myUQpDbomOpGDpd2aihudZD
	zrR+EwCwhNzZY9IzyeluCPj+jGm9Ha3UCdp6FAwBhGu5snG6FF3J3LiVtsjrjPil0K1d7q
	AJ3K+nl203/gWvmYBA5SpJbVJbD+Imz2CQ0Z0U/2ZclVhWO9QZVK3Kz/421z7+all5/92H
	6qcTokV8UGy/sg9L6woA4z0d5y0Fb5jA3lUqvcUAH3wLo1vrAAvWokI01N4OcQ==
ARC-Authentication-Results: i=1;
	mx1.freebsd.org;
	none
ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1734488838; a=rsa-sha256; cv=none;
	b=tsAq6v3hOibvqSX8xWvmL+VTcHdwk0+LpgLpgCSDohxkuMAOSFv5xBQ28FnVVgli/LCEAV
	SvIGho81iozadEXWmsqCTn1Ars9BxuxL+e8Oa1/ggii83vQ11RZMIQy6BQ3paQgGCOmmOL
	IEvlBkI642a84ljpKLSYtF0l3ZEJhVGTRxYeX7PkF6J2ijJxh4UUPxxx7Amd0x3aAI0+1P
	Z4Z3mZcEnHcKwu3Zmjsqz0OB7zXvrlX17BAGL2diiQlaqKnAP//P+/JhtaGbC5EeIuP/cj
	+BshMfmTwmwiLuqYjHD+bY0mFOd7i3MFfNlw+sQKnEHUwywIs0rPyk4Btdq2aw==
Received: from [10.9.4.95] (unknown [209.182.120.176])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(Client did not present a certificate)
	(Authenticated sender: kevans/mail)
	by smtp.freebsd.org (Postfix) with ESMTPSA id 4YCcyZ0RYwzhBZ;
	Wed, 18 Dec 2024 02:27:17 +0000 (UTC)
	(envelope-from kevans@FreeBSD.org)
Message-ID: <0d63a94d-2773-4efd-b789-0b753ab38b91@FreeBSD.org>
Date: Tue, 17 Dec 2024 20:27:16 -0600
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-arch
List-Help: <mailto:freebsd-arch+help@freebsd.org>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Subscribe: <mailto:freebsd-arch+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-arch+unsubscribe@freebsd.org>
Sender: owner-freebsd-arch@FreeBSD.org
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: freebsd-arch@freebsd.org
From: Kyle Evans <kevans@FreeBSD.org>
Subject: Removing shar(1)
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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