That's an accurate summary. Thanks. I've looked into the CCK, and since the mechanics of the 3 vs. 2 install are roughly the same, I'm tempted to think it'd work, but I didn't feel like digging into it with only an hour left to go before the weekend. :) The trademark issue was mentioned in the app dev group by Gervase Markham, who basically said the same thing as you.
On Jun 27, 5:49 pm, Nelson B Bolyard <[EMAIL PROTECTED]> wrote: > On 2008-06-27 08:55 PDT, tmountjr wrote that he is looking for a way > to package FF3 so that his University's root CA cert will be a trusted > CA cert for all who install his package, including those who are > upgrading from FF2. (Please correct that summary if it is inaccurate.) > > Two thoughts about that. (dunno if either will be helpful) > > 1. There is (or perhaps, was) a project called "Client Customization Kit" > that facilitated creating packaged browsers that contains all sorts of > differences from the base product. It easily handled configuration > changes in the file of user preferences, and IIRC, it was also capable > of installing new root CA certs into a cert DB. > > I don't know if it still is a live project, or if it works with FF3. > There is a version for FF2. You can read more about it > athttp://www.mozilla.org/projects/cck/and find more pages > athttp://search.yahoo.com/search?p=Mozilla+CCK > > 2. Mozilla's trademark policy says that if you change certain things > about Mozilla in your own build or packages, then you cannot release > your build using Mozilla trademarks (e.g. the Firefox brand name). > The set of trusted root CA certs is one of those things, I believe. > Seehttp://www.mozilla.org/projects/security/certs/policy/(last 2 > paragraphs) andhttp://www.mozilla.org/foundation/trademarks/policy.html > > The CCK page cited above suggests that if you limit distribution of the > modified browser to just "your company or institution" it may be OK to > retain the trademarks. Maybe Frank Hecker will say more about that. _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
