Hi all [Opening my pandora...].
A few months ago we started having problems with NSS (and OSX):
-Cannot load NSS libs from applet on Firefox 4 on MacOSX
http://forums.mozillazine.org/viewtopic.php?f=38&t=2165273
-Firefox 4 bad initialize on Mac OSX 10.6.7 This cause wrong
java.library.path, user.dir and @executable_path for Java libraries
(NSS/JSS)
https://bugzilla.mozilla.org/show_bug.cgi?id=654939
-Use @loader_path instead of @executable_path in internal name of
dylibs (Fix OSX support of Java-NSS)
https://bugzilla.mozilla.org/show_bug.cgi?id=578751
IMHO, this is some that needs some clarification, as Mozilla *IS*
supporting it developing JSS but at the same time saying "we do not
support it", and other options dont work properly due to some bugs
that need to be fixed...or not. Google Chrome works well and is taking
some advantage on this feature (too).
If we want Firefox to be used widely on bussiness/enterprise, then it
will be necessary to take an "official position", so PLEASE answer or
discuss the following:
-Does mozilla *WANT* Java use certificates stored on NSS to do
document signning?
-What about Java applets?
-Is mozilla going to *AVOID* Java use certificates, or consider this
as an "undocumented/undesired behaviour"?
-What about Java applets?
-Supporting this (or document sign with XAdES or any other advanced
systems) is one of mozilla's targets?
-Will patches which fix this issues merged (if correct) in branch, or
will they become marked as WONTFIX?
We dont want to rely on "undocumented/undesired" behaviour, and will
like to discuss whats the "official opinion" on this.
Consider the following example:
Signning a document with XAdES format with a certificate stored on NSS.
Can it be done? How should it be done?
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
