From: Clem Cole <clemc@ccc.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: shell escapes in utilities
Date: Wed, 2 Aug 2023 10:20:54 -0400 [thread overview]
Message-ID: <CAC20D2Mir_r2F8_DJ93wDhpJCkzjPP-udEux0AhX+scNX96nvQ@mail.gmail.com> (raw)
In-Reply-To: <bfda141b-43fd-e3e9-a495-68a3393910a4@tnetconsulting.net>
[-- Attachment #1.1: Type: text/plain, Size: 1181 bytes --]
On Tue, Aug 1, 2023 at 10:59 PM Grant Taylor via TUHS <tuhs@tuhs.org> wrote:
> I routinely use :'<,'>!sort or some similar external filter program on
> lines in the file that I'm working with.
>
No doubt. Pretty much the intended use. I've been doing that since I first
learned ed(1) and discovered I could do the same. It always seemed
natural and handy [sort(1), tr(1), and fmt(1) are probably the filters I
use the most over the years -- as I pretty much have the switches for the
same burned into the ROMs in my fingers]. If I had grown up with GUI's, I
suspect I might have used cut/paste in some manner to do the same thing
(for me, a less natural sequence).
As Ron points out, in using more(1) on the RS/6000 in maintenance mode,
shell escape on a multi-tasking system opens up some interesting security
paths/unintended side effects. Security is thought to get right. So many
places where good ideas can bite you when abused. It does not make it a
bad idea. But you need to consider other uses that might not behave the
way you planned.
This brings us back to Roz's warning to Mike: "*Always Watching.*"
[image: AlwaysWatching.png]
ᐧ
[-- Attachment #1.2: Type: text/html, Size: 2873 bytes --]
[-- Attachment #2: AlwaysWatching.png --]
[-- Type: image/png, Size: 409883 bytes --]
next prev parent reply other threads:[~2023-08-02 14:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 5:47 [TUHS] " ron minnich
2023-08-01 11:38 ` [TUHS] " Leah Neukirchen
2023-08-01 12:31 ` G. Branden Robinson
2023-08-01 20:33 ` Dave Horsfall
2023-08-01 20:40 ` arnold
2023-08-01 14:29 ` Skip Tavakkolian
2023-08-01 15:30 ` ron minnich
2023-08-01 18:43 ` Ron Natalie
2023-08-01 18:55 ` Niklas Karlsson
2023-08-01 20:48 ` Steffen Nurpmeso
2023-08-01 21:11 ` Ron Natalie
2023-08-01 21:52 ` Steffen Nurpmeso
2023-08-01 21:13 ` Niklas Karlsson
2023-08-01 21:19 ` Dave Horsfall
2023-08-02 3:01 ` Grant Taylor via TUHS
2023-08-02 3:42 ` Niklas Karlsson
2023-08-02 2:59 ` Grant Taylor via TUHS
2023-08-02 10:49 ` Rich Salz
2023-08-02 14:49 ` Grant Taylor via TUHS
2023-08-02 14:20 ` Clem Cole [this message]
2023-09-19 16:56 ` Ori Bernstein
2023-09-19 17:04 ` ron minnich
2023-08-01 15:36 ` Phil Budne
2023-08-01 15:37 ` Clem Cole
2023-08-01 15:37 ` Grant Taylor via TUHS
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=CAC20D2Mir_r2F8_DJ93wDhpJCkzjPP-udEux0AhX+scNX96nvQ@mail.gmail.com \
--to=clemc@ccc.com \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@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).