Firefox 3.6.2 Fixes Critical Security Hole

Mozilla addressed a critical security vulnerability with a minor Firefox update, bringing the browser to version 3.6.2. The vulnerability could potentially allow an attacker to “crash a victim’s browser and execute arbitrary code on his/her system.”

Users of FirefoxFirefoxFirefox 3.6 will have this update automatically downloaded and installed, but you can also manually apply it by selecting “Check for Updates…” from the Help menu.

The release notes for Firefox 3.6.2 can be found here. Mozilla Firefox 3.6.2 Release Notes




Firefox 3.6.2 Fixes Critical Security Hole

updated.

I had firefox crash me several times a few weeks ago.

I use mozilla seamonkey, does anyone else use it?

Nope.

oo, its good community browser

The SeaMonkey Project

from the site

About SeaMonkey

The SeaMonkey project is a community effort to develop the SeaMonkey all-in-one internet application suite. Such a software suite was previously made popular by Netscape and Mozilla, and the SeaMonkey project continues to develop and deliver high-quality updates as well as new features and improvements to this concept. Containing an Internet browser, email & newsgroup client, HTML editor, IRC chat and web development tools, SeaMonkey is sure to appeal to advanced users, web developers and corporate users.

powered by Mozilla SeaMonkey is built on the open source Mozilla Gecko engine, the same code which underlies the highly successful siblings Firefox and Thunderbird, as well as other projects such as Sunbird, Camino, Songbird and Miro. SeaMonkey benefits from the cross-fertilization with these other projects, by gaining (and contributing) new features and the ongoing security updates which are a modern necessity. The Mozilla Foundation provides hosting and legal backing for the SeaMonkey Project.
Organization
SeaMonkey Council

The SeaMonkey Council is the project leading team and can be contacted via the email address seamonkey-council@mozilla.org. Its responsibilities include release management (deciding when to cut releases and what code is included in a release; the release engineer of the Council is responsible for actually doing the release) and being the final instance for decisions about features when developers disagree. The SeaMonkey Council also decides on legal issues concerning the SeaMonkey project, in conjunction with the Mozilla Foundation, which provides legal backing for the project.

Members (in alphabetical order):

Mark Banner (Standard8)
Mark has been working on Mozilla since about 2004. He works mostly on the address book code, but has branched out into other areas. He has helped with a lot of the build work for the transition to toolkit. He is experienced with C++ but likes playing around with js as well.
Christian Biesinger (biesi)
Christian has been working on Mozilla for a few years; he mostly works in Gecko code, but also does UI patches occasionally. He wrote the image decoders for BMP and XBM files. He also wrote a Plan to make SeaMonkey use the "new toolkit".
Karsten Düsterloh (Mnyromyr)
Karsten's Mozilla addiction started as a Netscape 1.1 user and hasn't left him since - in late 2002 he published the first version of his Mozilla addon Mnenhy. His key focus is upon SeaMonkey's MailNews development.
Robert Kaiser (KaiRo) - project coordinator, release engineer
KaiRo is the head of MLP staff (Mozilla Localization Project) and has worked on localizing SeaMonkey since late 1999 (M11/M12). He's also doing the EarlyBlue and LCARStrek themes and has done some work on making some parts of the product localizeable and themable. See also KaiRo's blog and the German SeaMonkey site.
Ian Neal (IanN)
Ian does work on XUL/JS stuff (mainly UI but also some backend) with a little bit of simple C++ stuff thrown in. He peer reviews on help and has been actively involved in Mozilla development for about two years before the SeaMonkey project was started.
Neil Rashbrook (Neil) - SeaMonkey code module owner
Neil is the "module owner" of XPFE (most of the SeaMonkey-specific code), and a super-reviewer focussed on XPFE and MailNews. He has been very involved in all SeaMonkey related development for years.
Andrew Schultz (ajschult) - QA lead
Andrew has been working on Mozilla since 2002 and is the QA lead for SeaMonkey. When not working on QA, he fixes occasional bugs in Gecko and SeaMonkey code.

Project Area Owners and Peers

The SeaMonkey Project can be divided into several areas, which are listed on our project areas list. Each of those areas should have an owner and possibly several peers (people who know the code well enough to give reviews there), who together care about that area. The sum of those areas build a strong group of developers, who can move the SeaMonkey project forward.
Community

Additionally, there's a vibrant community surrounding those developers, see the SeaMonkey community page for how to get in touch with those people.
If you want to take an active role in testing or even developing SeaMonkey, getting involved with the project is fairly easy for anybody who can donate his time to our efforts.
Contact

For support and help or even development questions, please turn to our community which usually can help you faster and often better than our very small project steering team, the SeaMonkey Council.

If you have questions about legal issues, project management issues or topic that need to stay undisclosed to the wider public, please mail the SeaMonkey Council at seamonkey-council@mozilla.org.