Re: Re: Cryptic and X509 Certificates, DER Encoding etc.

Enzo Michelangeli (em@who.net)
Sat, 10 Oct 1998 18:32:27 +0800

• Next message: Antonomasia: "Re: ECC and timing attacks"
• Previous message: Ben Laurie: "Re: ECC and timing attacks"
• In reply to: Lucky Green: "RE: ECC and timing attacks"

If anybody is interested in implementing a persistent KeyStore for JDK 1.2
(writing a disk-based KeyStoreSpi class) I'm willing to contribute a dbm
implementation (Fddbm) that I'm anyway going to release under Berkeley
license. It has the same API as W3C's jddbm used in Jigsaw, but it's
completely different in the implementation: jdbm is a (still buggy) port to
Java of gdbm, whereas Fddbm is based on a sort of persistent HashTable,
using a C-style "heap" built on top of a RandomAccessFile. Interested
parties may contact me by e-mail; I'm postponing the public release because
I'm not really happy with the current mechanism used for managing the heap's
free list, which is a linked list (I'd prefer a b-tree for efficiency
reasons, should the list grows large).

Cheers --

Enzo

-----Original Message-----
From: Jeroen C. van Gelderen <gelderen@MEDIAPORT.ORG>
To: CRYPTIX-JAVA@HELPLETS.COM <CRYPTIX-JAVA@HELPLETS.COM>
Date: Friday, October 09, 1998 2:36 AM
Subject: Re: Cryptic and X509 Certificates, DER Encoding etc.

>From: Luke Taylor <luke@VALTECH.COM>
>>Does anyone know the situation regarding the use of the corresponding
>>sun.* classes in JDK1.2? There are classes for handling DER encoded
>>data and implementing certificates and so on. We've already done some
>>experiments with these, but I'm not sure whether they can legally be
>>used (even though they provide the underlying code for the Sun JCA
>>stuff).
>
>You should't be using the sun classes for the following reasons:
>1. It might be legal to use any installed classes, but shipping them with
>your product is almost certainly illegal.
>2. The classes and their contracts can change every moment.
>3. The classes are not guaranteed to be there (or function) in every JDK.
>
>We'd like to incorporate X509 support in the Cryptix suite, but we are
>concentrating on a JCE 1.2 release first. Please bear with us...
>
>
>>Also, while on the subject of sun - what is the legal status regarding
>>use of Sun's JCE provider implementation outside the states. Is it a
>>commercial product or is it only restricted by US export restrictions
>>and can be freely used once (illegally) exported?
>
>What I do know is that Cryptix is planning to ship an international version
>of JCE1.2 (running on both JDK 1.1 and 1.2). That version will be 100%
>compatible with Sun's. It will even include a 100% compatible
implementation
>of their default provider (SunJCE). In addition we will ship our own
Cryptix
>provider with the complete set of algorithms we currently support, but that
>will be a separate download.
>
>
>>The FAQ mentions that Cryptix 3.0.4 should work with JDK1.2 - is this
>>likely to be released soon(ish) ?
>
>Well, as you can read above we are in the process of changing a *lot* of
>code. The current product will be split in two pieces. The Cryptix JCE 1.2
>package (including the SunJCE provider) and the Cryptix Provider containing
>additional algorithms.
>
>Please be a bit patient, great things are coming but we all have a paid job
>as well :(
>
>Regards,
>Jeroen C. van Gelderen - gelderen@mediaport.org
>The Cryptix Development Team
>

• Next message: Antonomasia: "Re: ECC and timing attacks"
• Previous message: Ben Laurie: "Re: ECC and timing attacks"
• In reply to: Lucky Green: "RE: ECC and timing attacks"