Nelson B Bolyard wrote: > Yeah, I don't know why bugzilla didn't find that bug when I searched > using your name. I'm guessing it has a problem with the special > characters ú and ã.
Probably. It does not work for me neither. > I think you should attempt to diagnose the problem using the most > easily available information before trying the most difficult (code > debugging). I think it is quite possible that an examination of the > actual certificates involved will tell the story, and the code in > the module may not not need to be inspected. As far as I can tell, > you have not yet attached your certs to the bug. You've attached > CA certs, but not your own certs. I'm willing to look at your certs > when they're available to me. Ohh, I did. Look at 'Refered Certificates' (2008-05-17). I should use a better title like 'My Certs'. ;-) I am no expert on X.509 certs. But Thunderbird 2.0.0.14, MS Outlook and MS Live Mail worked very well with the certificates when they were inside their (mail programs) own Certificate Storages. Yes, the certs inside "Software Security Device" worked very well with TB. When I moved (deleted from the "Software Security Device") the certs to the USB Token, only TB have shown issues. It is the only that uses the standard PKCS #11. The others, of course, use MS Crypto API. I will try to discover tools to isolate the problem (certs, PKCS#11 module, NSS, PSM, TB). But I have discovered many things about TB looking only the sources. This is the reason that I also want to debug. > The MSVC compilations produce debug binaries (.exe or .dll files, and .pdb > files). The debugger built into MSVS 2005 does full source-level debugging > (no assembly code required, except for those functions that are written in > assembly language) using the binaries built that way. It's a very rich and > powerful source debugger. I cannot make VS 2005 show the source code while debugging an executable that was not created by a VS project. VS does not know where are the source code. Well, at least you confirmed that I can do "full source-level debugging using the binaries built that way (makefiles)". I will do my homework. :-) > I don't build the entire Thunderbird product, the way you did. I only > work on NSS, so I only build NSS. I download "nightly" builds of the > programs with which I want to test NSS, such as Thunderbird, and I replace > the downloaded NSS binaries with the ones I built, then I debug. As long > as I only try to set breakpoints in the code I actually compiled. it works > fine. > It is a good experience to build by myself. I can learn a bit about TB and its dependencies. And I have a chance to isolate the problem. From TB to NSS, since the PKCS#11 module has no debug info. After all, I am a TB user. Not an NSS one. Maybe my issued bug is not an NSS bug. Maybe it is a PKCS#11 module bug. Or a TB bug. Who knows? I will use some pkcs#11 tool from NSS to test my module. Cheers, Júlio _______________________________________________ dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
