Hello Pierre,

thanks a lot that sounds interesting. Could you attach your code to
FELIX-22 in jira? I'll look into it and report back.

In general, the current status is that I have an implementation that
doesn't need bouncecastle but still runs with foundation. It's not in
at the moment since I rework it to be an extension bundle. The good
thing about that is that we could potentially provide two
implementations, one that needs bouncycastle and one that doesn't.

As soon as I find some time to look over your patch I'll post a
proposal in this direction.

regards,

Karl

On 6/16/07, Pierre Parrend <[EMAIL PROTECTED]> wrote:

 Hello everybody,

  I have set up (together with Stephane) a patch for the validation of digital
signature of bundles for Felix.
 To give a answer to earlier inquiries from Karl Pauls:
- the code can be executed with Java 1.3
- the new JarFile(fileName, true) call, that is supposed to checked jar
signature is not sufficient (for two reasons: 1) files are verified at class
loading, and not at installation; 2) behavior is not compliant with OSGI R4
specs).

The code is contained in one single class, and relies on the bouncycastle bcprov
and bcmail libraries.

I propose to create in the felix trunk 2 directories to support the patch,
sfelix.doc and sfelix.jarvalidation directories. The Bouncycastle libs could be
set in the 'commons' dir.

 Should I create an entry for this in the Jira ?

best regards,

Pierre

--
Pierre Parrend
doctorant, moniteur
laboratoire CITI, 21, Av. Jean Capelle
69621 Villeurbanne Cedex
[EMAIL PROTECTED]
www.rzo.free.fr



--
Karl Pauls
[EMAIL PROTECTED]

Reply via email to