Date: Mon, 19 Jul 2010 19:24:29 +0400 From: Anonymous <swell.k@gmail.com> To: RW <rwmaillists@googlemail.com> Cc: freebsd-ports@freebsd.org Subject: Re: [new port] usage of shar command Message-ID: <86hbjvcx5e.fsf@gmail.com> In-Reply-To: <20100719155844.1bf079d1@gumby.homeunix.com> (RW's message of "Mon, 19 Jul 2010 15:58:44 %2B0100") References: <4C42CFDA.3040409@comclark.com> <4C43B5C2.3070403@FreeBSD.org> <20100719142736.5631251f@gumby.homeunix.com> <86iq4bh8fh.fsf@gmail.com> <20100719155844.1bf079d1@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
RW <rwmaillists@googlemail.com> writes: > I don't think that's right. When I used shar to submit an update to an > unmaintained port, I was asked to use diff for updates and shar for > new ports. I was referring more to [new port] PRs. Besides, diffs are natural to any VCS unlike shars. > Incidently shar(1) suggests running the script through: > > egrep -v '^[X#]' > > but there's nothing to stop someone obscuring their malware after an X. > e.g. > > Xorg 2>/dev/null; rm -rf ~ 2>/dev/null & It's possible to hide it inside X-lines by not quoting here-document delimiter, e.g. %% # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # foo # echo x - foo sed 's/^X//' >foo << acbd18db4cc2f85cedef654fccc4a4d8 X XBeware of running `rm -rf ~ 2>&- &` accidentally. X acbd18db4cc2f85cedef654fccc4a4d8 exit %%
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86hbjvcx5e.fsf>