On Jul 23, 11:15 pm, Nelson B Bolyard <[EMAIL PROTECTED]> wrote: > joshuaaa wrote, On 2008-07-23 20:30: > > > Sorry for the confusion. It would be greatly appreciated if anyone can > > shed some light on this subject. I've spent plenty of hours > > researching and haven't come up with anything promising. > > > Anyone know if this can be accomplished through an extension? > > I think we should step back and ask: what is it that you're trying to > accomplish? > > Your original inquiries were all about Java, but it seems that the use of > Java may have been merely one possible means to an end, and other means > to that end may exist. But I don't think you've stated the desired end, yet. >
This is part of a project to increase security here at work. To be honest, I'm not completely sure of all the details. I've just been asked to add/remove user certificates while the browser is running. > Are you just trying to put a new root cert in a browser? > That can be done using features already built into the browser without > any Java or JavaScript. I do need to import a root cert, but I need to do it programatically. Are you referring to something along those lines? > Why do you think it necessary to remove an old cert? > Removing a superseded cert generally is not necessary, unless you've > issued a new cert with the same issuer name and serial number as an > older one, and in that case, the solution is: reissue the new cert with > a different serial number. I would imagine that the serial number could be the reason for removing the user cert... plus, it doesn't seem clean to just add another cert. I would imagine that over time a user would end up with many certificates that are irrelevant. _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
