On 2012-04-04 13:04, helpcrypto helpcrypto wrote: > IIRC, NSS doesnt have an official mantainer on Mozilla bugs, isnt it? > If this happens, its probably the source of many problems here. I have > filed a few bugs and most of then arent even checked. > To be fair & honest, im also guilty of that, but i dont feel confident > enough to edit Mozilla source. > Could any expert make a workshop and teach us(me) how to ? > I thinks this could be a quite simple > start:https://bugzilla.mozilla.org/show_bug.cgi?id=670895 > > Having this "unified keystore", has ever been discussed between > mozilla and unix people? > What did they decide?
I think this remains something that only vendors like Microsoft, Google and Apple can do; the general *NIX lot is too divided to settle on such a thing. Mozilla should IMO rather hook into the other vendors cryptographic solution, possibly at the expense of NSS. According to a college of mine Chrome even use the platform's SSL implementation! Well, not in *NIX since there is no such thing... In JDK/JRE Oracle (previously SUN) have native support for CAPI which is "unclean" but is what Windows(-only) developers would prefer. Then you get away from spicing your server-apps with a gazillion static password configs that fill absolutely no security purpose! Anders -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
