> I did stop and reconsider your suggestion about removing the star server's
> redundant decrypt/re-encrypt step. It could be done without introducing a
> ppp layer (which has several of the aforementioned design requirements
> problems I won't go into here). Unfortunately, if I did that, the initial
> handshaking a client box does with the star server (to identify itself and
> the type of connection it wants to make, etc) wouldn't be encrypted or
> cryptographically verified either (unless I did it myself, and right now all
> the encryption is neatly handled by ssh, which I already mentioned not
> wanting to modify).
That's not correct... if you set the encryption type to none the
connection and port forwarding are not encrypted, but the handshake still
is, using password, host key, or requiring both. You can make a fully
authenticated non-encrypted connection. I like running the popular "sleep"
program as the main command, and using port forwarding for what you do,
since you reject running ppp over ssh.
I'm running 19-pre10ac2+smp patches, as I recall ac4 or 5 are out, I just
stopped upgrading when I got stability. If you run uni you should be able
to drop in the new kernel, push the excryption overhead to the endpoints,
and have nearly no work on the star server.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/