Use files.
./program-cli | (
read -r
printf "%s\n" "$REPLY" > /tmp/a
) > /tmp/b
fooify /tmp/a
barify /tmp/b
sed is the canonical paragraph mangler. It's worth spending a bit to grok how
that is true.
tr -d '\r' | sed '/^$/!{H;d;};p;x;s/\n/ /g;'
Gutenberg lines are CRLF-terminated so `tr` is needed.
> I can get away with a less powerful shell as long as it has tab
> completion. Tab completion just saves so much time.
Directly typing into a shell is a red flag. ie. a shell is just another REPL
and should be driven by your editor.
This a) documents your work, and b) toggles the developer bit
Stunnel supports requiring client cert verification, ie. client cert is known
or was signed by a given CA. Willing to trade pubkeys for PKI?
See "requireCert" and the /verify.*/ options in
https://www.stunnel.org/static/stunnel.html
Patrick
Looking at https://github.com/mkj/dropbear -- it seems like every sshd just
grows to include things like X11/port forwarding
Would rather have a small sshd with docs that say run netcat if you want
port-forwarding.
