On Fri, Mar 05, 2004 at 10:54:41AM +0100, Erwin van der Koogh wrote: > Anyone know of an opersource project called juice? > Yes - http://juicy.sourceforge.net/
In my mind, the naming should somehow reflect the aim of the project (which is something that also seems to be less than clear to me in the proposal). I had a very quick look at the code that was linked to in the proposal, and although I may be missing something (I don't claim to know much about java) it did seem that the code there was very limited in what it did - only rsa operations and a couple of digest algoritms. What's the long term plan? 1. just sticking to those (which might be justified since these are the most used and the most expensive part of the operation) ? 2. full jce implementation? 3. full interface to openssl? 4. something entirely different? If it is either 2 or 3, then I'd say that either jce or openssl should be part of the name (using openssl as part of the name might be a problem, but I'm sure Ben Laurie could help with that). Just my $.02 as someone who has used openssl for a long time, and wouldn't mind an easy way to access it from java. vh Mads Toftum -- `Darn it, who spiked my coffee with water?!' - lwall
