Re: Removing shar(1)

From: Renato Botelho <garga_at_FreeBSD.org>
Date: Thu, 19 Dec 2024 12:45:02 UTC
On 18/12/24 19:13, Cy Schubert wrote:
> In message <0d63a94d-2773-4efd-b789-0b753ab38b91@FreeBSD.org>, Kyle Evans
> write
> s:
>> 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
> 
> I use it at $JOB, produce a shar file, cut/paste into a terminal.
> 
> Should it be removed I'll perform the repo surgery to base a port on it.

As mentioned in this thread, you can use `tar` to create shar file:

# tar -cf file.share --format shar ./foo

-- 
Renato Botelho