Citrix Metaframe Xp with Feature Release 1 applied is able to use SSL.  The
encryption available on all versions of Citrix (from 1.8, at least) is 40-,
56-, and 128-bit RC5.  You can also choose to use 128-bit RC5 for logon
only.  I think 128-bt RC5 ought to be pretty decent and shouldn't require
the additional SSH overhead.

I do not think Windows Terminal Services is encrypted, although, I believe
the logon is the usual Windows Hash-style.

K

----- Original Message -----
From: "tack" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 29, 2002 9:16 AM
Subject: [BAWUG] Re: wireless digest, Vol 1 #797 - 15 msgs


> > As for the different levels of encryption that Metaframe provides I do
> > not know what the differences are. I have used Windows NT/2000 terminal
> > services which is based on the Citrix code (I believe?) and have had
> > good luck tunneling it over ssh with the "High" encryption that Terminal
> > Services provides enabled.
>
> How mature is the citrix scheme?  If it's a proprietary, non peer reviewed
> cryptosystem, I would agree with the above and tunnel it through
> something that is open and peer reviewed like ssh-2.  Particularly of
> interest in a wireless network is key exchange.  I might consider
> something using diffie-hellman somewhat safe over wireless.  But just to
> be sure, ssh tunneling, or ssl with key rotation is probably the way to
> go.
>
> tack
>
> --
> general wireless list, a bawug thing <http://www.bawug.org/>
> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
>

--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless

Reply via email to