Bob Lord wrote:
> Ben Bucksch wrote:
>
>> But in the distribution, PSM will still be separate, right? This is
>> important, because distribution of crypto product is considerably
>> harder than non-cryotp ones, even after the changes in the U.S.
>> export rules.
>
> PSM will still be a separate module after the integration work is
> complete. It just means you don't have to download an XPI file we
> produce.
> However...
>
> The current plan is that SSL and other crypto operations will *not*
> be built by default. This means if you don't want crypto, you don't
> have to do anything special, and PSM will not be built. If you *do*
> want crypto, you'll have to set an environment variable before you
> build. When you do that, PSM and NSS will be pulled and built on
> your system.
In which form will it be built?
What I need (on one hand) is the same as today: I need a fully
functional Mozilla suite without crypto, i.e. where the US export law
don't apply. However, I need to provide an add-on (with a small download
size, today 1.2 MB or so), which makes this same build crypto-enabled.
This makes it possible to use mirrors like Tucows*, which don't allow
crypto, for distribution of the bulk of the app, and provide the crypto
software as add-on from non-US mirrors.
If this were not possible, the changes would worse the situation for me.
So, please make sure, the add-on, as available today, will still be
possible.
*Does anybody know about the Redhat and Debian policies for crypto? All
of Mozilla going into non-US wouldn't be good at all.
