Choosing an implementation language

Gary Ellison gary.ellison at sun.com
Mon Oct 20 12:59:02 EDT 2003


>>>>> " " == Eric Rescorla <ekr at rtfm.com> writes:

 > Tyler Close <tyler at 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 at sun.com
       "Knowledge speaks, but wisdom listens." -- Jimi Hendrix

---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo at metzdowd.com



More information about the cryptography mailing list