From: Homer Parker <hparker@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Seamonkey vs Mozilla cage match round two
Date: Sat, 18 Nov 2006 16:35:43 -0600 [thread overview]
Message-ID: <1163889344.9260.3.camel@laptop> (raw)
In-Reply-To: <20061118144602.GA28579@crowfix.com>
On Sat, 2006-11-18 at 06:46 -0800, felix@crowfix.com wrote:
> > Another thing you should be aware of: As development (and even
> > bugfixing) for Mozilla has ceased quite a while ago the last release
> has
> > a number of security bugs that are well known and wide open. Any
> program
> > using parts of Mozilla are therefor vulnerable as well. For that
> reason
> > you shouldn't be using Mozilla and instead switch over to Firefox or
> > Seamonkey. It will be removed from the tree sooner rather than
> later.
>
> I use mozilla without javascript, java, etc, which probably eliminates
> most of the security problems.
Ok, you use it like that. I bet there are people that don't though and
the mozilla team doesn't have the time/resources to fix the security
problems, and upstream has dropped support. If you want to continue to
use it with those problems, great... Dump it in your overlay and use
it.. Just remember it's unsupported and has security problems and if it
breaks you get to keep both pieces ;)
--
Homer Parker <hparker@gentoo.org>
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-18 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 7:20 [gentoo-amd64] Seamonkey vs Mozilla cage match round two felix
2006-11-18 7:45 ` Michael Weyershäuser
2006-11-18 14:46 ` felix
2006-11-18 22:35 ` Homer Parker [this message]
2006-11-19 0:42 ` felix
2006-11-19 2:34 ` Michael Weyershäuser
2006-11-19 4:12 ` felix
2006-11-19 7:26 ` [gentoo-amd64] " Duncan
[not found] <1163942462.6978.6.camel@ShadowBook.Workgroup>
2006-11-19 13:21 ` [gentoo-amd64] " B Nice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1163889344.9260.3.camel@laptop \
--to=hparker@gentoo.org \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox