Thats kinda what I'm working towards. Eventually I want to take my testing and split it off into a seperate option instead of making every jar file made by signtool in that format. Right now I'm stuck on getting NSS to compile on windows. I got to the point last night where I was ready to put my hand through my monitor.... Last errors I got were failed compile of the utf8.c
make[2]: Entering directory `/cygdrive/c/mozilla/security/nss/lib/util' cl -FoWINNT5.1_DBG.OBJ/utf8.obj -c -Od -Z7 -MD -W3 -nologo -GT -DXP_PC -DDEBUG -D_DEBUG -UNDEBUG -DDEB UG_jeff -DWIN32 -D_WINDOWS -D_X86_ -DWINNT -I../../../../dist/WINNT5.1_DBG.OBJ/include -I../../../../ dist/public/nss -I../../../../dist/private/nss -I../../../../dist/public/dbm c:/mozilla/security/nss/ lib/util/utf8.c utf8.c c:/mozilla\security\nss\lib\util\utf8.c(35) : error C2059: syntax error : '<<' c:/mozilla\security\nss\lib\util\utf8.c(37) : error C2059: syntax error : '==' c:/mozilla\security\nss\lib\util\utf8.c(39) : error C2059: syntax error : '>>' make[2]: *** [WINNT5.1_DBG.OBJ/utf8.obj] Error 2 make[2]: Leaving directory `/cygdrive/c/mozilla/security/nss/lib/util' make[1]: *** [libs] Error 2 make[1]: Leaving directory `/cygdrive/c/mozilla/security/nss/lib' make: *** [libs] Error 2
It's been one thing after another. I've read tons of posts on mozillazine.org on getting Firebird/Mozilla/Thunderbird to compile on Windows only using free tools. A bunch have been able to do it and I have found many answers to problems that I did have but now I'm stuck for the moment. I've spent the last two days nearly straight working on this. Didn't really do any work yesterday, kinda been getting obsessed over this.
I did some looking in the XPI install code and got lost...
But I did find code relating to the Cert stuff in mozilla/xpinstall/src/
files: CertReader.cpp, nsXPInstallManager.cpp and nxXPITriggerInfo.cpp Specifically in the nxXPITriggerInfo.cpp there is.
void
nsXPITriggerItem::SetPrincipal(nsIPrincipal* aPrincipal)
{
mPrincipal = aPrincipal;
// aPrincipal can be null for various failure cases.
// see bug 213894 for an example.
// nsXPInstallManager::OnCertAvailable can be called with a null principal
// and it can also force a null principal.
if (!aPrincipal)
return; PRBool hasCert;
aPrincipal->GetHasCertificate(&hasCert);
if (hasCert) {
nsXPIDLCString cName;
aPrincipal->GetCommonName(getter_Copies(cName));
mCertName = NS_ConvertUTF8toUCS2(cName);
}
}
Jeff Klawiter
Jean-Marc Desperrier wrote:
Nelson B wrote:
Now, apparently, beginning a couple years ago, mozilla requires the .[rd]sa
files to be first. As far as I'm concerned, that's a bug in mozilla.
The versions of mozilla that require that are incompatible with nearly
ALL the jar files made before that.
The current Mozilla expects *XPI* files to have this form to be signed.
Signed jar files work normally. Maybe because it's the java plug-in that checks them.
The patch you wrote will do what you apparently want it to do, namely put the .[dr]sa file first in the META-INF directory. You're welcome to use that patch all you want. But I think the right thing for mozilla is to fix the jar parsing code, so that the file order doesn't matter.
Unfortunately, the legacy is really strong by now and it will be difficult to go back for xpi files.
A specific flag in signtool that would create files with an xpi extension and the special ordering Mozilla expects could be useful.
_______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
