In response to "Frank Evan Perdicaro" <[EMAIL PROTECTED]>, who says,
> >Recall that for a dial-up connection, you are typically running IP on
> >the raw layer, TCP on that, PPP on that, then perhaps a VPN on that,
> >perhaps with SSL on that, then VNC on top, and finally the user is doing
> >something.
"Jonathan Morton" <[EMAIL PROTECTED]> says,
> Swap IP for PPP. PPP runs on the raw layer, IP on top of that, any
> VPN goes here followed by another IP layer, TCP on top of that, SSL
> on that followed by VNC. Please, don't mangle the OSI stack any more
> than BSD already has.
Ignoring, for the moment, the order of the layers, I'm wondering if perhaps
I don't understand what I thought I did about SSH and VPN (I hate it when
that happens.) If I had a VPN in place, would I need to run (or benefit from
running) SSH on top of it? I was interested in SSH for it's authentication
and encryption (and possibly for compression) features, all which I might
reasonably expect of a VPN implementation. I know one *could* use a VPN as a
transport for SSH traffic, and I'm sure there's some pathological case where
one might *want to*, but it the simple case ("I don't want my precious
packets running naked through the streets of the Internet."), isn't one or
the other --- VPN or SSH --- sufficient?
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
