Re: Issue 5.1) SSH End of message directive

[Wes Hardaker <wjhns1@hardakers.net>]

>>>>> On Thu, 19 Feb 2004 20:02:52 -0500, Ed Roskos <ed.roskos@utstar.com> said:

Ed> But SSH, as I see it, must fill a particular need, and that is
Ed> scripting.  How do you explain to someone that they cannot just
Ed> cut-and-paste, they must calculate bytes for the message, while
Ed> they are playing around getting their scripts right in the first
Ed> pass?

Oh, sorry if you thought I was advocating byte counters.  I wasn't.  I
was just pointing out there are two ways to get around problems like
this: forced escaping and byte lengths.

Note that BEEP has byte length counters in it as well, which I've
pointed out before because I wasn't sure script-writers would want it.

Ed> What we need for SSH is a simple way to stream in your messages
Ed> which does not introduce possible security breaches.  I think
Ed> we pretty much have such a method.

Which is?  disallowing CDATA?  That'd be unpopular I bet.

-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>