| 1 |
Brad Plant wrote: |
| 2 |
>>>Ok, I just checked the security handbook and it only mentions |
| 3 |
>>>glsa-check. Ok, its probably my bad... but shouldnt emerge world |
| 4 |
>>>merge security updates too? |
| 5 |
>> |
| 6 |
>>"world" is only the contents of /var/lib/portage/world and their (deep |
| 7 |
>>if using --deep) dependencies. Integration of glsa-check in the form of |
| 8 |
>>"emerge --security" or some such is planned. An "all" target is also |
| 9 |
>>planned. |
| 10 |
> |
| 11 |
> Running "emerge -pv depclean" should show any packages not covered by |
| 12 |
> "world" right? |
| 13 |
|
| 14 |
Unfortunately, that is *too* correct. Unfortunate in that both |
| 15 |
--depclean and --update only consider USE flags defined in make.conf and |
| 16 |
package.use (and embedded in .tbz2s when using binaries). This means |
| 17 |
that if package "foo" depends on package "bar" due to USE flag "baz" |
| 18 |
being enabled at install time and "baz" is subsequently disabled, "bar" |
| 19 |
becomes an orphaned package as far as the graph goes - even though it is |
| 20 |
still required. |
| 21 |
|
| 22 |
What does this mean in terms of security? The "only install what you |
| 23 |
need" rule is twice as important. Until portage is a little smarter, I |
| 24 |
would consider a "healthy" system to be one where `emerge -uDNvp world` |
| 25 |
shows no differing USE flags and both `emerge -p --depclean` and |
| 26 |
`revdep-rebuild -p` show no packages. |
| 27 |
|
| 28 |
-- |
| 29 |
Jason Stubbs |
| 30 |
-- |
| 31 |
gentoo-security@g.o mailing list |
Archives