Hi,
At the time, it was easier to have something with a prompt (even if it
told you the only option was to quit and how to do it) rather than
confuse a user who wouldn't understand a blank terminal that echoed
lines back at you.
Cheers,
John
On 24/05/2009, at 9:08 PM, Kent Fredric wrote:
On Sat, May 23, 2009 at 12:59 PM, John Collis <[email protected]>
wrote:
Hi,
Last time I had to do this, I simply wrote a simple command in C,
that would wait for a character and then exit. It doesn't have to be
too complicated. You could easily print a simple prompt (to alert
any user who looks at a terminal) and then wait. For security just
don't use getchar() or any function that is susceptible to a buffer
overflow attack and you should be fine. Using a script for this type
of usage is not generally regarded as secure.
What reasons are against using /bin/cat ?
input = output ( so you can type garbage and hit enter to check the
connections working still )
and ^D or ^C to disconnect.
--
Kent
perl -e "print substr( \"edrgmaM SPA nocomil.i...@tfrken\", \$_ *
3, 3 ) for ( 9,8,0,7,1,6,5,4,3,2 );
John Collis - [email protected]
Technology Development
IndraNet Technologies Ltd.
http://www.indranet-technologies.com/
