Re: Removing shar(1)

Cy Schubert <[email protected]>
Newsgroups gmane.os.freebsd.architechture
Message-ID <[email protected]>
In message <[email protected]>, Renato 
Botelho w
rites:
> On 18/12/24 19:13, Cy Schubert wrote:
> > In message <[email protected]>, 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

And there's GNU sharutils as well.

I've simply extracted it into its own repo for use in a port. Seems the 
consensus of the reviewers of https://reviews.freebsd.org/D48130 agree. As 
I said before, this is not the proper place to discuss the removal. There 
is active discussion on FreeBSD-arch.

>
> -- 
> Renato Botelho


-- 
Cheers,
Cy Schubert <[email protected]>
FreeBSD UNIX:  <[email protected]>   Web:  https://FreeBSD.org
NTP:           <[email protected]>    Web:  https://nwtime.org

			e^(i*pi)+1=0
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.