From: Rainer Groesslinger <scandium@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Security Problems: xmule, lmule
Date: Wed, 20 Aug 2003 01:32:47 +0200 [thread overview]
Message-ID: <200308200132.48140.scandium@gentoo.org> (raw)
In-Reply-To: <1061335558.14357.7.camel@localhost>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1028 bytes --]
On Wednesday 20 August 2003 01:25, Patrick Lauer wrote:
> > 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 did that, just didn't mention it in my email...if you re-sync you
should get the new ebuilds + package.mask
> > 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.
that einfo is at pkg_postinst() so everbody should see it (at least if
nothing else is merged immediatly afterwards ;)
--
Rainer Groesslinger
http://dev.gentoo.org/~scandium/
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-19 23:32 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
2003-08-19 23:32 ` Rainer Groesslinger [this message]
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=200308200132.48140.scandium@gentoo.org \
--to=scandium@gentoo.org \
--cc=gentoo-dev@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