Re: DICOM on SSH?
- From: "Wences" <wgrillo@xxxxxxxxx>
- Date: 9 Jul 2006 07:53:53 -0700
You use an SSH tunnel.
If Box-1 is running the SSH server, and this med app is listening on
port 104, in Box-2 you do something like:
ssh -C -L 2323:127.0.0.1:104 Box-1
(If you're using putty, that's allow compression and add a local
tunnel).
And leave it running. Then, again in Box-2, (on another Window) you
tell the med app to connect to localhost on port 2323. It's connection
will be caught by SSH, encrypted, and sent to Box-1. In Box-1, the SSH
server will decrypt it and send it to 127.0.0.1 (from Box-1's point of
view, i.e: Box-1) on port 104, so the med app will receive it.
SpreadTooThin wrote:
Hi I have a medical imaging application that I normally communicates
with its peers via TCP/IP.
There is a client and a server portion to this application that listens
on a port and client that
sends to that port. (Typically port 104).
My question is how do I use ssh under this application? ie. What do I
do so that the
communications between the client and server go through ssh.
The only configuration parameters that these applications have (that is
relevant to tcp/ip)
is a host name and port number.
TIA.
.
- Follow-Ups:
- Re: DICOM on SSH?
- From: SpreadTooThin
- Re: DICOM on SSH?
- References:
- DICOM on SSH?
- From: SpreadTooThin
- DICOM on SSH?
- Prev by Date: Which shell / terminaltype for SSH Tectia for Windows?
- Next by Date: Re: Which shell / terminaltype for SSH Tectia for Windows?
- Previous by thread: DICOM on SSH?
- Next by thread: Re: DICOM on SSH?
- Index(es):
Relevant Pages
|