-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
gentoo-sources-2.4.22-r3 (released yesterday) doesn't fix any latestst
security problems. in fact, it is identical to 2.4.22-r2.
i wonder why it has been released and marked as stable...
pb
- --
Public Key: http://teleinfo.tu.kielce.pl/~pb/gpg.asc
-
Not sure, but after upgrading to it my nvidia and eth0 were killed.
Seemd nvidia wanted to reemerge into the r2 modules dir, and eth0 just
for some odd reason refused to connect. Ouch. I don't recommend the
upgrade until a few weeks has gone by when things can be ironed out.
pb wrote:
-BEG
On 01/07/04 pb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> gentoo-sources-2.4.22-r3 (released yesterday) doesn't fix any latestst
> security problems. in fact, it is identical to 2.4.22-r2.
> i wonder why it has been released and marked as stable...
How did you check this ?
Ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
>>gentoo-sources-2.4.22-r3 (released yesterday) doesn't fix any latestst
>>security problems. in fact, it is identical to 2.4.22-r2.
>>i wonder why it has been released and marked as stable...
>
>
> How did you check this ?
>
# cd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El Miércoles, 07 de Enero de 2004 16:24, Marius Mauch escribió:
> On 01/07/04 pb wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > gentoo-sources-2.4.22-r3 (released yesterday) doesn't fix any latestst
> > security problems. in fact
On 01/07/04 Alberto Garcia Hierro wrote:
> Differences are _trivial_.
I wasn't talking about the differences but the vulnerability.
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothi
Marius Mauch wrote:
On 01/07/04 Alberto Garcia Hierro wrote:
Differences are _trivial_.
I wasn't talking about the differences but the vulnerability.
So, does gentoo-sources-2.4.22r3 address this recent vulnerability or
not? :-)
I just finished upgrading everything to 2.4.22r2, so if I'm
On 01/07/04 Jonathan Nichols wrote:
> So, does gentoo-sources-2.4.22r3 address this recent vulnerability or
> not? :-)
>
> I just finished upgrading everything to 2.4.22r2, so if I'm going to
> reboot stuff, now is a good time. ;)
Both r2 and r3 were fixed yesterday, however to be sure use r3
On Thu, 2004-01-08 at 04:56, Marius Mauch wrote:
> Both r2 and r3 were fixed yesterday, however to be sure use r3 (the
> patch was added to r2 after it was already deployed, so it's hard to say
> wether your installation has it).
Sorry to prolong the thread, but isn't this not supposed to happen?
pb wrote:
gentoo-sources-2.4.22-r3 (released yesterday) doesn't fix any latestst
security problems. in fact, it is identical to 2.4.22-r2.
i wonder why it has been released and marked as stable...
pb
--
Public Key: http://teleinfo.tu.kielce.pl/~pb/gpg.asc
Glad I decided to wait to upgrade to r3, a
10 matches
Mail list logo