Deployment:Deploying Firefox: Difference between revisions

Deployment:Deploying Firefox (view source)

Revision as of 02:15, 11 November 2007

139 bytes removed , 11 November 2007

confusing note moved to talk

Sj

181

edits

@@ Line 187: / Line 187: @@
 http://ftp.mozilla.org/pub/mozilla.org/security/export-notice
-The '''CCATS''' number '''G023895''' (''for what?  all firefox or mozilla versions?  specific versions?'') makes it easier for companies to file when they include NSS or Mozilla Applications such as Firefox which use NSS.
+NSS 3.4 requested a '''CCATS''' commodity classification id '''G023895''' to make it easier for companies to file when they include NSS or Mozilla Applications such as Firefox which use NSS.
-: ''note : the associated '''ECCN''' is likely 5D002.c.1 (TSU unrestricted, EAR 740.13(e)); though one could request a review of a binary to have it reclassified under 5D992.b.1; see Frank Hecker's Jan 2005 post at http://ftp.mozilla.org/pub/mozilla.org/security/export-notice )''
+: ''note : the associated '''ECCN''' for software packages is likely to be 5D002.c.1 (TSU unrestricted, via EAR 740.13(e)).  One could theoretically request a review of a binary to have it reclassified under 5D992.b.1, but it's not known whether anyone has.  See Frank Hecker's Jan 2005 post http://ftp.mozilla.org/pub/mozilla.org/security/export-notice )''
-This CCATS filing covers all the crypto operations used in the Mozilla code base, including SSL and S/MIME.  Strictly speaking, Mozilla did not have to file for a CCATS number because the NSS crypto code is "''publicly available''" and the binaries are built from purely open source software.
+This CCATS filing covers all the crypto operations used in the Mozilla code base, including SSL and S/MIME.
 More information on exporting products made from Open Source can be found at https://www.bis.doc.gov/encryption/enc.htm and http://www.access.gpo.gov/bis/ear/ear_data.html