24 Mar
2017
24 Mar
'17
4:34 p.m.
On 3/24/17 1:06 AM, shawn wilson wrote:
I actually have strong opinions about this (read:
disagreements). Your
shell shouldn't know about connect() - I guess allowing writing to
/dev/eth0 would work for me.
Yeah, but nobody wants to do that.
But in bash, IIRC that damn ghost file
thing is like half of the files in source and it helps nothing.
What does this mean?
Maybe
if the point was to allow some remote shell (like X does) I could see
it (but than I'd scream about the security implications about
something like that). And I'll say again - why? You want a socket -
nc, ncat, socat - pick one - don't abuse your shell.
You always have the option of not compiling it into the shell.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet(a)case.edu http://cnswww.cns.cwru.edu/~chet/