Co:Z has a configuration option that allows you to either tunnel data connections in the original ssh connection (the default) or to use un-tunneled, clear sockets. In the latter case the data is unencrypted, which can be appropriate for secure networks. Using un-tunneled hipersockets really screams, since the protocol stack is very efficient.
For more details on configuration options, see: http://dovetail.com/docs/coz/config.html#config_launcher_optional Kirk Wolf Dovetailed Technologies http://dovetail.com On Thu, May 29, 2008 at 9:20 AM, David Andrews <[EMAIL PROTECTED]> wrote: > On Thu, 2008-05-29 at 08:25 -0500, Kirk Wolf wrote: > > You might also consider in some cases offloading the processing to an > > IFL or other Linux processor. > > Our free Co:Z toolkit makes this simple to do, and in the case of an > > IFL you can use clear-channel hipersockets. > > Kirk, what do you mean by "clear-channel hipersockets"? Co:Z is using > ssh for data transport, and ssh always encrypts... no? > > (A little googling suggests that encryption can be defeated if you have > the HPN patchset installed on your OpenSSH end nodes. Is this what > you're referring to?) > > -- > David Andrews > A. Duda and Sons, Inc. > [EMAIL PROTECTED] > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
