"Ohaya" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Nelson, > > Comments below, interspersed... > > Jim > > > > Nelson Bolyard wrote: > > > > Ohaya wrote: > > > > > I realized that (that NS 4.x and PSM 1.x were not actively supported). > > > The problem is that this location is using NS 4.79, and I don't have > > > much choice. > > > > > > What I would like to do is see if the problem that I'm seeing is due to > > > the PSM being 1.1 (vs. 1.2, or possibly 1.4), so I was hoping if some > > > kind soul had 1.2, they could provide it for just a test. > > > > Well, one thing you could do is try to import this cert using mozilla 1.6 > > final, or 1.7 beta, and see if it works better there. If not, then you > > can be reasonably certain that your cert won't work in PSM 1.x either. > > and you will save your self some trouble. In that case, the problem > > may be in the cert itself. > > A couple of comments here: > > - I know that I won't be able to get them to change browser version, > i.e., I'm stuck with trying to get this problem resolved with the > existing NS 4.79, but I may be able to get them to go to PSM 1.2. > > - My first thought when I started investigating this problem was that it > might be a problem with the CA cert, as you suggested. But, our help > desk people are claiming that tons of other people have imported this > same CA cert without encountering the problem I saw. I know those > "other people" are all on NS 4.79, but I'm not 100% sure if they're > still using PSM 1.2 (trying to find out). That's why I was hoping that > if I could find PSM 1.2 somewhere, I could try installing it on just one > of the workstations that I saw the problem on, then try the import > again. If the problem disappears, then I can tell that the problem was > with PSM 1.1, and then try to make the case for going to PSM 1.2. > > I've searched and searched, and I find it hard to believe that someone, > somewhere, doesn't have PSM 1.2 on some archive or something... > > > > > > > Also, as mentioned, I found PSM 1.4, I think, as a .JAR file, but can't > > > figure out how to install it. > > > > Have you tried visiting the .jar file with a file:// URL? > > I really don't remember how that stuff worked, but I sort of remember > > that the browser had to process the file as it would if the file was > > being downloaded from a URL. MIME type was probably relevant also. > > > > Sorry, wish I remembered more. > > Hah! You're better than you remembered :)!!! Doing a File->Open Page, > then browsing to the .JAR file in Navigator did the install :)!! > > Jim
Hi Nelson, FYI, I tried importing the cert into PSM 1.4, and I am seeing the same behavior that I saw when I used PSM 1.1 at the office. This *seems* to indicate that there might be something wrong with the cert? Also FYI, just as an FYI, I downloaded the cert onto my hard drive, and then in Windows, clicked on it. I got a popup saying something like "Invalid Security Object". Does anyone know specifically what could be wrong with this certificate that would cause it to behave this way in PSM and in Windows? Jim _______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
