[14683] in cryptography@c2.net mail archive
Re: Choosing an implementation language
daemon@ATHENA.MIT.EDU (Gary Ellison)
Mon Oct 20 14:19:02 2003
X-Original-To: cryptography@metzdowd.com
X-Original-To: cryptography@metzdowd.com
Date: Mon, 20 Oct 2003 09:59:02 -0700
From: Gary Ellison <gary.ellison@sun.com>
To: EKR <ekr@rtfm.com>
Cc: Tyler Close <tyler@waterken.com>, cryptography@metzdowd.com
In-Reply-To: <kjvfr5ao86.fsf@romeo.rtfm.com>
Reply-To: gary.ellison@sun.com
>>>>> " " == Eric Rescorla <ekr@rtfm.com> writes:
> Tyler Close <tyler@waterken.com> writes:
>> On Thursday 02 October 2003 09:21, Jill Ramonsky wrote:
>> > I was thinking of doing a C++ implentation with classes and
>> > templates and stuff. (By contrast OpenSSL is a C
>> > implementation). Anyone got any thoughts on that?
>>
>> Given the nature of recent, and past, bugs discovered in the
>> OpenSSL implementation, it makes more sense to implement in a
>> memory-safe language, such as python, java or squeak. Using a VM
>> hosted language will limit the pool of possible users, but might
>> create a more loyal user base.
> There's already a Java SSL with a simple API:
> http://www.rtfm.com/puretls/
There is also a standardized and widely distributed implementation and
API. JSSE is bundled with J2SE as of v 1.4:
http://java.sun.com/products/jsse/
--
mailto:gfe@sun.com
"Knowledge speaks, but wisdom listens." -- Jimi Hendrix
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com
