On Mon, 2005-01-24 at 10:07 +0000, Ian Hastie wrote: > On Monday 24 January 2005 08:58, Xavier-Francois Roblot wrote: > > Hi, the last unstable version of evolution 2.0.3-r1 was released to fix > > bug #79183 according to the ChangeLog. Since I am a curious guy, I > > wanted to have a look at what this bug is. But when I search for it on > > bugs.gentoo.org, I get: > > > > You are not authorized to access bug #79183. > > > > Well, I didn't know some bugs are so bad that the have to be kept > > secret :o) > > I'm a bit curious too so I had a look for some more information. The > ChangeLog says this > > *evolution-2.0.2-r1 (23 Jan 2005) > > 23 Jan 2005; Mike Gardiner <[EMAIL PROTECTED]> > +files/evolution-2-CAN-2005-0102.patch, +evolution-2.0.2-r1.ebuild, > +evolution-2.0.3-r1.ebuild: > New revisions for 2.0.2 and 2.0.3, including CAN-2005-0102 patch. See bug > #79183 > > So there is the reference to CAN-2005-0102, which is the problem that the > patch is meant to fix. I don't know if this is the only, or even best, place > to find this information, but Google helped me find this > > http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0102 > > Which says > > ** RESERVED ** This candidate has been reserved by an organization or > individual that will use it when announcing a new security problem. When the > candidate has been publicized, the details for this candidate will be > provided. > > > I guess I'll have to install without knowing the truth... > > Yes, for now at least.
So it is for a security issue that we cannot access the bug. On the other hand, it is not difficult to have a look at the (very short) corresponding patch: /usr/portage/mail-client/evolution/files/evolution-2-CAN-2005-0102.patch from which one can deduce what the bug was ;o) Xavier -- [email protected] mailing list
