Closed Bug 10914 Opened 26 years ago Closed 25 years ago

Need export license for 5.0 Beta

Categories

(Core :: Internationalization, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: msanz, Assigned: lord)

References

Details

(Whiteboard: [PDT+])

Need to apply for export license for Beta 1.
Blocks: 7228
Assignee: chofmann → lord
The forms have been filed.
Status: NEW → ASSIGNED
do we still need this in the band new world?>
Keywords: beta1
PDT+
Whiteboard: [PDT+]
All binary products which contain encryption code must continue to comply with US export regulations. In this case, the strong-crypto version of PSM for Communicator has been granted retail approval. That means that the Seamonkey beta will ship with strong-crypto. There will be no weak-crypto version. Marking bug as FIXED.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Changed QA contact to Cindy Roberts. Cindy, could you reassign this to the right person to verify this?
QA Contact: teruko → roberts
QA Contact: roberts → michaell
Adding "Need marketing to verify." in Status Summary
Whiteboard: [PDT+] → [PDT+] Need marketing to verify.
This is not fixed. All software that we ship goes out with a commercial license that governs the use of the software. An example of this can be seen by going to about:license in 4.x. I need to get this boilerplate for the beta. Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [PDT+] Need marketing to verify. → [PDT+]
do we have strong crypto in the seamonkey builds right now? the win32 installer is named seamonkey32e with 'e' historically being the designation for export level/56bit security. Is it/should it be our convention to use e for strong security now?
oops. My bad. I confused this with another bug that says we need a License for beta. We still need that. This one, however, is fixed as Bob says. Marking fixed.
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Verifying.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.