Mozilla to Include Crypto
Willy Wonka passed us the news that Mozilla's
M14 release will include crypotography on the branch.
If you'd care to add your eyeballs to the debugging process, please do: Christine Begle posts in the n.p.m.seamonkey newsgroup, "We need help from the Mozilla community to test the crypto-enabled M14 candidate builds. Some tests and test plans will be posted to mozilla.org sometime on Tuesday."
That's today, folks.
To clarify this a little more: the security library for Netscape Communicator (which will also be in the iPlanet PSM binaries that will work with Mozilla) incorporates proprietary code from RSA Security, and some of that code implements the RSA public key algorithm, on which RSA Security has a patent in the U.S.
Once the RSA patent expires then other people in the U.S. may write and release code implementing the RSA algorithm without requiring a patent license from RSA. However the code supplied by RSA Security will still be proprietary. What the expiration of the patent will allow is creation of an alternative RSA implementation which is open source and can be freely used with the Mozilla source base.
I believe the patent on the RSA algorithm expires this autumn.
September 20, 2000 (which actually is in the summer, but just barely). And yes, patents normally are for 17 years.
I'm seeing a lot of posts that ask about this or that. Try downloading Mozilla. Mozilla currently supports Javascript up to 1.5 and CSS 1 & 2. Download the build - give it a shot.
The SSL code will be included in the tip - not the mozilla tree. This means - no one will see the code that is owned by RSA. So using cvs on the tree wont get you all the crypto code - it will probably download at least one small binary file that includes the patented RSA code. Which later this year will fall into public domain.
Don't forget to help out on the Mozilla project - Mozilla runs great on Mac, Linux, Win32 and all sorts of variant UNIX operating systems as well as OS's I've never even heard of.
Joseph Elwell.
I'd like to appeal to everyone. If you like Linux and especially Open Source Software, please download this release of Mozilla (and future releases as well) and use it, abuse it, and break it. Then, report those bugs! This is going to be one of the biggest coups for Open Source Software and show a lot of detractors that OSS is a viable method for developing quality software. It will also blow away a lot of FUD concerning security issues, etc. of OSS (because it's open.) Thanks.
kuro5hin.org
Co-founder and designer at Music Nearby: http://musicnearby.com
One important note: the crypto in M14 will not be Open Source. Rather, M14 will incorporate hooks which will be usable with a binary-only crypto module from iPlanet (the offspring of the Netscape-Mozilla alliance.) For more on the situation, read this mozillazine post.
IAAL,BIANLY
When you're done banding together to implement RSA without violating their patents, please drop us a line. (Have fun storming the castle!)
it's bug #22687
Vote early (and as the old joke goes, vote often)
W
-------------------
-------------------
This is my SIG. There are many like it, but this one is mine.
Besides, we don't want Mozilla to be like the bug-laden products of some companies out there...do we?
Don't pick on RedHat like that -- they're still Open Source and could use our support now that their stock's been tanking.
Cheers,
ZicoKnows@hotmail.com
http://www.bxa.doc.gov/Encryption/licchart.htm
Product
Previous Licensing Mechanism
Update99 Licensing Mechanism
Technical Review
Reporting
Source Code (publicly available, unrestricted)
IL/ELA
TSU
No3,4
No
Source Code (publicly available with restrictions)
IL/ELA
ENC
No3,4
Yes
Notes:
3. No review of foreign products(s)
4. BXA Notification at time of export is required
Returned Peace Corps IT Volunteer
The net will not be what we demand, but what we make it. Build it well.
From the ngLayout FAQ:
..." ("Microsoft Outlines XML Support in IE5 Beta 2" at http://www.xml.com/xml/pub/98/10/ie5-2.html)
For XML formatting, why is Gecko supporting CSS rather than XSL in the first release?
Simple: CSS1 is a finished, fully adopted, and mature two-year-old standard; XSL isn't done yet. As Tim Bray, the coeditor of the XML standard, has written:
"Microsoft's XSL efforts are very impressive, but (readers will pardon us being something of a broken record on this subject) XSL is in the future. We are convinced that from the point of view of the largest number of users, the most important things that Microsoft could do in IE 5 would be:
1.Ensure interoperability of XML and stylesheets with other browsers, and
2.Build in conformance to existing, stable, well-understood standards such as CSS 1.0.
Innovation, of course, is fine and necessary, and we salute Microsoft's leadership in this area. But innovation needs to be built on a foundation of interoperability and playing by existing well-understood rules." He further adds that "It seems obvious to me that for anyone who wants to deploy XML in production mode right now, XML + CSS is the way to go
-=snip=-
I understand their reasoning, but damnit, I want my XSL! It's very weird giving XML demos in IE.
Since the U.S. govt slackened off some of the export regulations, the crypto can be available as long as it is not knowingly exported to a restricted country. Also, since mozilla is using hooks to a binary - the same way the shockwave flash plugin works - one can develop one's own crypto modules if so desired.
Desperation is a stinky cologne
Curses! http://www.mozillazine.org is blocked by SurfWatch! Just when I was about to get a stable browser that works, the filtering companies decide open source software is against their morals :-(