From: Patrick Lauer <gentoo@toso-digitals.de>
To: Rainer Groesslinger <scandium@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Security Problems: xmule, lmule
Date: 20 Aug 2003 01:25:58 +0200 [thread overview]
Message-ID: <1061335558.14357.7.camel@localhost> (raw)
In-Reply-To: <200308200108.34719.scandium@gentoo.org>
On Wed, 2003-08-20 at 01:08, Rainer Groesslinger wrote:
> On Wednesday 20 August 2003 00:47, Patrick Lauer wrote:
[snip]
> > Please discourage the use of lmule and xmule until fixed versions are
> > available.
>
> lmule was removed from the tree several weeks ago because it isn't
> developed anymore and unsupported for a few months now.
ok
> The problem - indeed - is, that even their latest unstable release
> (1.5.6a) doesn't fix the problem and I observe xmule sharply and am
> waiting for a fixed release or at least a patch.
I recommend masking _all_ versions at the moment and issuing a GLSA.
Maybe I'm overreacting, but I do not wish to have my computer rooted :)
> I added an einfo about the security hole in all the xmule ebuilds and I
> hope they release 1.4.4 or something soon (which will immediatly be
> arch of course)
That's good, but I don't think it's adequate since not everybody
reinstalls xmule every day _and_ reads all einfo lines scrolling by.
Btw, what's the official way for reporting vulnerabilities?
On the website I found almost nothing ... maybe this could be made
easier? Or did I miss something really obvious?
Thanks for the almost instantaneous response,
Patrick Lauer
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-19 23:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 22:47 [gentoo-dev] Security Problems: xmule, lmule Patrick Lauer
2003-08-19 23:08 ` Rainer Groesslinger
2003-08-19 23:19 ` Rainer Groesslinger
2003-08-19 23:25 ` Patrick Lauer [this message]
2003-08-19 23:32 ` Rainer Groesslinger
2003-08-19 23:51 ` Owen Gunden
2003-08-20 2:28 ` Georgi Georgiev
2003-08-27 13:43 ` Rainer Groesslinger
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=1061335558.14357.7.camel@localhost \
--to=gentoo@toso-digitals.de \
--cc=gentoo-dev@gentoo.org \
--cc=scandium@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