I'm not entirely certain what their internal deployments and rollouts are, to be fair. My primary knowledge comes from conferring with people within the organizations.
I should point out that the second is an example of a situation where such paranoia on the part of the MIS staff would be well-founded. Compliance is not something that you can leave up to the corporate users; the administration of the network is trained on compliance issues and knows how to make things auditable. Pushing that to the desktop opens many many possible locations where something can go wrong (a custom-compiled web browsing executable that doesn't enforce policies, etc). I'll see if I can get the name of the product that the educational institution is using. -Kyle H On Dec 5, 2007 12:36 AM, Nelson Bolyard <[EMAIL PROTECTED]> wrote: > Kyle Hamilton wrote, On 2007-12-04 23:03: > > Two short, practical examples, which are gleaned from reality (though > > I am not at liberty to state of what organizations I speak): > > And these organizations are locked-in to Mozilla products now, because > IE won't work for them, right? > > > _______________________________________________ > dev-tech-crypto mailing list > dev-tech-crypto@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-tech-crypto > _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto