[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Summary: SSH concerns
Thanks to everyone for responding. The summary seems to be that there
aren't concerns with the application itself. Nobody reported a case
where the application actually spat out information that needed to be
dealt with by the expect script.
A number of people indicated that they were still doing stuff over telnet.
Those who did use ssh invoked it with -T. One person recommended -o
"Batchmode=yes" and UserKnownHostsFile=/dev/null to make the app a bit
more deterministic. [This introduces a security assumption that may be
dangerous in some environments.] That same author suggests that the
more paranoid might push around host files.
One person complained about the multi-stage effort required to create
public/private key pairs were derived.
As to the reference to sendmail and interface accessibility, one person
put it this way:
I'm strongly infavour of any protocol that can be done eaisly with a human
driving it at the keyboard, being able to telnet to port 25 and manually
enter SMTP commands is a good example of a protocol that can be eaisly
emulated by a human for diagnostic purposes. It's invaluable in an
Thanks again for your comments.
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.