CVE-2011-4966: RESERVED
CVE-2011-5244: TODO: check
CVE-2012-5535: RESERVED
CVE-2012-5560: RESERVED
CVE-2012-5885: TODO: check
CVE-2012-5886: TODO: check
CVE-2012-5887: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker.
CVE-2011-2487: RESERVED
CVE-2011-4966: RESERVED
CVE-2011-5244: TODO: check
CVE-2012-5535: RESERVED
CVE-2012-5560: RESERVED
CVE-2012-5885: TODO: check
CVE-2012-5886: TODO: check
CVE-2012-5887: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the
CVE-2012-5530: RESERVED
CVE-2012-5534: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-5785: TODO: check
CVE-2012-5883: TODO: check
CVE-2012-5884: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
CVE-2012-5785: TODO: check
CVE-2012-5883: TODO: check
CVE-2012-5884: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
CVE-2012-4417: RESERVED
CVE-2012-5241: RESERVED
CVE-2012-5785: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To
CVE-2012-: RESERVED
CVE-2012-5241: RESERVED
CVE-2012-5371: RESERVED
CVE-2012-5785: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the
CVE-2012-: RESERVED
CVE-2012-5241: RESERVED
CVE-2012-5371: RESERVED
CVE-2012-5785: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the
CVE-2012-0698: RESERVED
CVE-2012-4573: RESERVED
CVE-2012-5241: RESERVED
CVE-2012-5784: TODO: check
CVE-2012-5785: TODO: check
CVE-2012-5786: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the
CVE-2012-4564: RESERVED
CVE-2012-4575: RESERVED
CVE-2012-5285: RESERVED
CVE-2012-5286: RESERVED
CVE-2012-5287: RESERVED
CVE-2012-5673: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
CVE-2012-4557: RESERVED
CVE-2012-4565: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-4550: RESERVED
CVE-2012-4552: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-4194: RESERVED
CVE-2012-4195: RESERVED
CVE-2012-4196: RESERVED
CVE-2012-4544: RESERVED
CVE-2012-5339: TODO: check
CVE-2012-5368: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the
CVE-2012-4529: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-4520: RESERVED
CVE-2012-4528: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-3427: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-4462: RESERVED
CVE-2012-4480: RESERVED
CVE-2012-5351: TODO: check
CVE-2012-5352: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the
CVE-2012-3524: TODO: Needs more checking, probably this should be fixed in the
affected apps like spice?
CVE-2012-4424: RESERVED
CVE-2012-4425: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates
CVE-2012-3524: TODO: Needs more checking, probably this should be fixed in the
affected apps like spice?
CVE-2012-4424: RESERVED
CVE-2012-4425: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates
CVE-2012-3524: TODO: Needs more checking, probably this should be fixed in the
affected apps like spice?
CVE-2012-4424: RESERVED
CVE-2012-4425: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates
CVE-2012-3524: TODO: Needs more checking, probably this should be fixed in the
affected apps like spice?
CVE-2012-4424: RESERVED
CVE-2012-4425: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates
CVE-2012-4922: TODO: check
CVE-2012-4929: TODO: check
CVE-2012-4930: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
CVE-2012-4414: RESERVED
CVE-2012-4416: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-4405: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2011-3090: TODO: check
CVE-2012-4406: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2002-2439: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-3543: RESERVED
CVE-2012-3552: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2011-5129: TODO: check
CVE-2012-3543: RESERVED
CVE-2012-3552: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To
CVE-2012-3533: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-3512: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-1525: TODO: check
CVE-2012-1535: TODO: check
CVE-2012-2049: TODO: check
CVE-2012-2050: TODO: check
CVE-2012-2051: TODO: check
CVE-2012-3416: RESERVED
CVE-2012-4147: TODO: check
CVE-2012-4148: TODO: check
CVE-2012-4149: TODO: check
CVE-2012-4150: TODO: check
CVE-2012-4151: TODO: check
CVE-2012-3440: TODO: check
CVE-2012-3461: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-3446: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
the feature in
the tracker itself?
Thanks.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http
CVE-2012-3412: RESERVED
CVE-2012-3422: RESERVED
CVE-2012-3423: RESERVED
CVE-2012-3429: RESERVED
CVE-2012-3448: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker
CVE-2011-3464: TODO: check
CVE-2012-0283: TODO: check
CVE-2012-1969: RESERVED
CVE-2012-2662: RESERVED
CVE-2012-2688: TODO: check
CVE-2012-3365: TODO: check
CVE-2012-3367: RESERVED
CVE-2012-3411: RESERVED
CVE-2012-3424: RESERVED
CVE-2012-3431: RESERVED
CVE-2012-3435: RESERVED
CVE-2012-3437:
CVE-2011-3464: TODO: check
CVE-2012-0283: TODO: check
CVE-2012-2662: RESERVED
CVE-2012-2688: TODO: check
CVE-2012-3365: TODO: check
CVE-2012-3367: RESERVED
CVE-2012-3411: RESERVED
CVE-2012-3817: TODO: check
CVE-2012-3868: TODO: check
CVE-2012-4024: TODO: check
CVE-2012-4025: TODO: check
CVE-2012-2662: RESERVED
CVE-2012-3367: RESERVED
CVE-2012-3411: RESERVED
CVE-2012-4024: TODO: check
CVE-2012-4025: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the
CVE-2012-2662: RESERVED
CVE-2012-3367: RESERVED
CVE-2012-3411: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To
CVE-2012-0283: TODO: check
CVE-2012-2662: RESERVED
CVE-2012-3365: TODO: check
CVE-2012-3367: RESERVED
CVE-2012-3411: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the
CVE-2012-0283: RESERVED
CVE-2012-0540: RESERVED
CVE-2012-1689: RESERVED
CVE-2012-1734: RESERVED
CVE-2012-1735: RESERVED
CVE-2012-1756: RESERVED
CVE-2012-1757: RESERVED
CVE-2012-3401: RESERVED
CVE-2012-3410: RESERVED
CVE-2012-3411: RESERVED
--
The output might be a bit terse, but the above ids
CVE-2012-0283: RESERVED
CVE-2012-3410: RESERVED
CVE-2012-3411: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To
CVE-2012-3410: RESERVED
CVE-2012-3411: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-2744: RESERVED
CVE-2012-2745: RESERVED
CVE-2012-3864: RESERVED
CVE-2012-3865: RESERVED
CVE-2012-3866: RESERVED
CVE-2012-3867: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
CVE-2012-3386: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
https://access.redhat.com/security/cve/?year=1999:
2012-07-08 06:42:55 ERROR 404: Not Found.
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script
CVE-2012-3374: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-3375: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-3818: TODO: check
CVE-2012-3825: TODO: check
CVE-2012-3826: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
CVE-2012-3236: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-3364: RESERVED
CVE-2012-3366: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2011-5095: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2011-5095: TODO: check
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2011-4605: RESERVED
CVE-2012-2678: RESERVED
CVE-2012-2746: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To
CVE-2011-5094: TODO: check
CVE-2012-2088: RESERVED
CVE-2012-2113: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To
CVE-2012-2652: RESERVED
CVE-2012-2679: RESERVED
CVE-2012-2695: RESERVED
CVE-2012-2736: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the
CVE-2012-0218: RESERVED
CVE-2012-1167: RESERVED
CVE-2012-1711: RESERVED
CVE-2012-1713: RESERVED
CVE-2012-1716: RESERVED
CVE-2012-1717: RESERVED
CVE-2012-1718: RESERVED
CVE-2012-1719: RESERVED
CVE-2012-1721: RESERVED
CVE-2012-1722: RESERVED
CVE-2012-1723: RESERVED
CVE-2012-1724: RESERVED
CVE-2011-5092: TODO: check
CVE-2012-2034: RESERVED
CVE-2012-2035: RESERVED
CVE-2012-2036: RESERVED
CVE-2012-2037: RESERVED
CVE-2012-2038: RESERVED
CVE-2012-2039: RESERVED
CVE-2012-2652: RESERVED
CVE-2012-2672: RESERVED
CVE-2012-2673: RESERVED
CVE-2012-2676: RESERVED
CVE-2012-2677: RESERVED
--
CVE-2011-5092: TODO: check
CVE-2012-0441: TODO: check
CVE-2012-1253: TODO: check
CVE-2012-1820: RESERVED
CVE-2012-2137: RESERVED
CVE-2012-2372: RESERVED
CVE-2012-2652: RESERVED
CVE-2012-2654: RESERVED
CVE-2012-2672: RESERVED
CVE-2012-3105: TODO: check
--
The output might be a bit terse, but
CVE-2012-1253: RESERVED
CVE-2012-2652: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To UNSUBSCRIBE, email to
CVE-2012-2652: RESERVED
CVE-2012-2655: RESERVED
CVE-2012-2664: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
--
To
CVE-2011-2082: RESERVED
CVE-2011-4459: RESERVED
CVE-2011-4460: RESERVED
CVE-2012-2098: RESERVED
CVE-2012-2389: RESERVED
CVE-2012-2390: RESERVED
CVE-2012-2391: RESERVED
CVE-2012-2392: RESERVED
CVE-2012-2393: RESERVED
CVE-2012-2394: RESERVED
CVE-2012-2395: RESERVED
CVE-2012-2625: RESERVED
CVE-2011-3102: TODO: check
CVE-2012-2130: RESERVED
CVE-2012-2373: RESERVED
CVE-2012-2374: RESERVED
CVE-2012-2375: RESERVED
CVE-2012-2625: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the
CVE-2011-3620: RESERVED
CVE-2012-1587: RESERVED
CVE-2012-1616: RESERVED
CVE-2012-2132: RESERVED
CVE-2012-2134: RESERVED
CVE-2012-2139: RESERVED
CVE-2012-2140: RESERVED
CVE-2012-2147: RESERVED
CVE-2012-2213: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
) then put it behind
some js.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org
.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201102132012.39397.geiss
Package: security-tracker
Severity: wishlist
Hi,
It would be great to have a report like the one generated by bin/reserved-but-
public.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ
-1
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201101260211.28228.geiss
Package: security-tracker
Severity: wishlist
In order to apply some CSS the generated code needs to be friendlier, for
example:
* include ids in the tags
* use divs instead of tables
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email
that we lack of
proper tools to for example track files that are moved between packages.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
painful.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/hrqkl0$17
Michael's changes went live.)
Not sure if the inodes table needs to be flushed or if even code changes are
needed.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject
Hi,
It's been at least a week since the dtsa-candidates page is broken. I
haven't had time and probably won't have to investigate. Could anyone please
check what's wrong? thanks
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email
.
Thanks for spotting this. I will try to rectify this tomorrow.
I did remove it some time ago, but I should have probably rebuilt the
database from scratch.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker
Nico Golde wrote:
FWIW, ack :) I have a smart bookmark in my browser for that anyway, their
information is really useful in most cases.
Do you have any other link that should be added?
Gentoo's bugzilla and Ubuntu's launchpad didn't seem to be of much use.
Cheers,
--
Raphael Geissert
broke it due to bad SQL.
Michael, please fix it soon
.
Regards,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
I was wondering, shouldn't kfreebsd-* be added to the list of squeeze
architectures so that the tracker is aware of it? or should we wait until
the number of built packages is almost the same as for the linux archs?
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org
Package: security-tracker
Severity: wishlist
It would be great to provide such report, as to have a link to it on the DDPO.
Cheers,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
signature.asc
Description: This is a digitally signed message part.
701 - 778 of 778 matches
Mail list logo