| 1 |
How about starting with putting the GLSA's in the tree? |
| 2 |
|
| 3 |
That would be step 1. |
| 4 |
|
| 5 |
Then an emerge sync would give you new security information too. |
| 6 |
or perhaps an glsa-ebuild? |
| 7 |
|
| 8 |
After this, I agree it would be best to add a --security option. |
| 9 |
|
| 10 |
IMHO this should work, so emerge -u world --security (or -S - or is that |
| 11 |
too close to -s?) would look at all the upgrades suggested by the world |
| 12 |
- and then check against the glsa's and see if any of them have are |
| 13 |
mentioned here. The glsa's should be named after the package version |
| 14 |
that fixes this issue, that way it would be easy to check and upgrade if |
| 15 |
the currently installed is older. |
| 16 |
|
| 17 |
Better solutions are welcome - but are they as easy to implement as |
| 18 |
this? |
| 19 |
-- |
| 20 |
Regards, |
| 21 |
Klavs Klavsen, GSEC - kl@××××.dk - http://www.vsen.dk |
| 22 |
PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62 |
| 23 |
See my new CMS Hosting Service at http://www.VirkPaaNettet.dk |
| 24 |
|
| 25 |
Working with Unix is like wrestling a worthy opponent. |
| 26 |
Working with windows is like attacking a small whining child |
| 27 |
who is carrying a .38. |
Archives