HP3000-L Archives

February 2008, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Wed, 27 Feb 2008 07:41:01 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Ian Warner wrote:
> Thanks to all for the reply on sockets, a second question
>
> Does SSH encrypt data being sent or is pre-encryption needed?

SSH (and SSL, SCP, TLS, et al) encrypts data in transit only.  Using the 
standard APIs, you don't see the encrypted forms (you just supply the keys).

The 3000 can be an SCP client (barely).  I don't know of any server side 
things that were fully ported.

If you use an intermediate SSH host, you can use tunnels (have succeeded 
with both Putty and SSHClient) to encrypt some standard plaintext 
traffic to the 3000.  Setup a linux host "close" to the 3000 (e.g., on 
the same subnet, or if it has two NICs, use it as a gateway to the 
3000's network).  This can be used to encrypt telnet and NSVT, but since 
it's a single channel, doesn't work for FTP or Reflections "fast" file 
transfer.

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2