Op di 25-05-2004, om 17:49 schreef Jason A. Pattie:
> | [EMAIL PROTECTED] wrote:
> | | But, the bulk of your comment is correct. The data is
un-encrypted.
> | |
> | | We're working on tunnelling this through SSH, but it's not
complete yet.
> |
> | Jim, how do you plan on tunnelling UDP traffic us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| On Mon, 24 May 2004, Jason A. Pattie wrote:
|
|
| [EMAIL PROTECTED] wrote:
| | But, the bulk of your comment is correct. The data is un-encrypted.
| |
| | We're working on tunnelling this through SSH, but it's not complete ye
On Mon, 24 May 2004, Jason A. Pattie wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> [EMAIL PROTECTED] wrote:
> | But, the bulk of your comment is correct. The data is un-encrypted.
> |
> | We're working on tunnelling this through SSH, but it's not complete yet.
>
> Jim, how do you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| But, the bulk of your comment is correct. The data is un-encrypted.
|
| We're working on tunnelling this through SSH, but it's not complete yet.
Jim, how do you plan on tunnelling UDP traffic using SSH? The XDMCP
chooser/log
On Mon, 24 May 2004, Otto [iso-8859-15] Kekäläinen wrote:
> Hello!
>
> As I understand, all traffic in a between a running client and server in
> LTSP i sent with XDMCP, which is not an encrypted protocol. So that if there
> is a sniffer on the network, he'll catch all usernames and password f
Hello!
As I understand, all traffic in a between a running client and server in
LTSP i sent with XDMCP, which is not an encrypted protocol. So that if there
is a sniffer on the network, he'll catch all usernames and password from all
logins, right?
What can I do to encrypt or scramble my traf
