M14 to Contain Crypto Code!
Monday February 28th, 2000
That's right, Mozilla.org plans to land the newly opened crypto code on the M14 branch, which will "allow [mozilla.org] to get crypto out to the public, without affecting stability of the tip." But before they push a final M14 out, they want to get some good testing done of the crypto-enabled builds, and we plan to help them out with surveys or polls to gauge user opinion. We should know more Tuesday about when crypto will land in the branch; we'll let you know as soon as we hear anything.
You can read more about the crypto landing in Christine Begle's post to the n.p.m.seamonkey newsgroup.
#8 Crypto... really?
Tuesday February 29th, 2000 3:25 AM
You are replying to this message
There was some confusing stuff earlier about crypto meaning that it would include hooks and stuff but not actual cryptographic code...
So does this announcement mean that it will really, out-of-the-box just work with secure sites, when I download a binary? Will I be able to just go and buy a book? (Not from amazon.com, of course, because I'm boycotting them re patents, as everyone else should be. But from somewhere else. :)
I think the answer is yes, but I just wanted to check :)
BTW, as for the person who asked about the remaining M14 bugs, I don't know anything specific about it, but I imagine the answer as to when they will be fixed is "later". They'll slip to a later milestone - M15, M16, M17, etc., as usual: that happens every milestone. I'm sure there are some M14 bugs that were originally M10 bugs or so ;)
I'm really impressed with the bug-fixing recently; the two most critical bugs I've been concerned about for ages (incorrect font size and referrer) have both been squelched.
The only two things that make it a pain to use Mozilla right now [well, apart from severe crashes in the last nightly build I picked up but I assume that's a temporary thing] are (a) lack of drag-and-drop of links between windows, which means you can't "reuse" windows when you have more than one open, and (b) lack of security support... at least *one* of these will be fixed. :)