| 1 |
Steve Long wrote: |
| 2 |
> Daniel Drake wrote: |
| 3 |
>> Construction of a dynamic website for tracking kernel security issues. |
| 4 |
>> There are too many of them and too many kernels to do this through the |
| 5 |
>> normal GLSA process, and currently users are kept in the dark about |
| 6 |
>> fixed security issues. |
| 7 |
> Who put's up the "fixed security issues"? |
| 8 |
|
| 9 |
Nobody, that's the point of this project. We currently don't have GLSA |
| 10 |
or any other form of security announcements for kernel packages. |
| 11 |
|
| 12 |
>> Tim had started developing a site for this ("KISS") but it was never |
| 13 |
>> finished and had the large downside that it relies upon an operator |
| 14 |
>> duplicating lots of information from bugzilla and the ebuild tree into |
| 15 |
>> KISS. |
| 16 |
>> |
| 17 |
>> Such a system would be able to automatically pull a large proportion of |
| 18 |
>> the required information relatively easily. It would offer functionality |
| 19 |
>> to allow users to sign up for security announcements and fixes for their |
| 20 |
>> kernel(s) of choice, as well as feeding the same info into a mailing |
| 21 |
>> list for all kernels. |
| 22 |
> |
| 23 |
> If you can put it thru repoman (or some other script) it can be automated. |
| 24 |
|
| 25 |
It can't be pulled at that level. But as I said, yes, it can be |
| 26 |
automated, thanks for agreeing ;) |
| 27 |
|
| 28 |
The existing data which needs to be aggregated is mostly held on bugzilla. |
| 29 |
|
| 30 |
Daniel |
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives