[Standards-JIG] JEP-0060: Comments on latest draft.
spendleton at movsoftware.com
Mon Jun 28 16:26:00 UTC 2004
I have no idea how you would write a TLS implementation for a closed-source
stack such as Windows Mobile (Win32 subset). However, using OpenSSL as a
replacement SSL implementation would be doable, and might be preferable. It
is definitely worth considering, but would require a stable port of OpenSSL
to be installed on the client. Of course, SSL with both encryption and
compression enabled has other issues on mobile and embedded platforms as
well (such as CPU/memory usage on devices with limited power/memory).
Of particular interest to me is if server developers have TLS compression
enabled on their SSL implementations? I have only tested with Jabber, Inc's
server. Also of interest, can s2s connections be made via SSL using the
various server implementations?
From: Ralph Meijer [mailto:jabber.org at ralphm.ik.nu]
Sent: Monday, June 28, 2004 3:18 AM
To: pendleto at movsoftware.com; Jabber protocol discussion list
Subject: Re: [Standards-JIG] JEP-0060: Comments on latest draft.
On Sun, Jun 27, 2004 at 03:03:31PM -0400, Stephen Pendleton wrote:
> Just FYI: TLS compression would work, but doesn't exist on some
> platforms currently (Windows Mobile, PocketPC, Smartphones, etc). I am
> not sure about other non-Unix non-Win32 platforms. I have been hoping
> that a server developer could offer some solution to this issue at
> some point.
I'm confused. If TLS is not available, but other server side solutions would
be implementable (surely you'd need something on the client side as well),
why not just write a TLS implementation?
More information about the Standards