Recent Features
| |||||||||||||
Minimizing packagesMinimizing packagesPosted Jun 25, 2007 7:23 UTC (Mon) by flewellyn (subscriber, #5047)In reply to: Minimizing packages by jmorris42 Parent article: Counting vulnerabilities
I remember this nonsense from the days when I ran Red Hat Linux, back before Fedora and RHEL.
DPKG-based distros seem better at allowing you to select "required" versus "recommended"
Gentoo and other source-based distros, to me, seem to have the best solution: build only with
(Log in to post comments)
Minimizing packages Posted Jun 25, 2007 22:03 UTC (Mon) by njs (guest, #40338) [Link] >Gentoo and other source-based distros, to me, seem to have the best solution: build only with what you actually need, and disable features you don't need to use. Thus, excess packages get pruned from the dependency tree and you end up with less clutter (and, not incidentally, fewer possible vulnerabilities).
But the trade-off is that every box ends up running its own unique mix of code. Security-wise, this is good in that it increases diversity (so it's less likely someone will be able to pwn *all* Gentoo boxes), but reduces scrutiny on the actual code and interactions present on any particular box (so it's more likely that any particular Gentoo box *can* be pwned, which is probably what most sysadmins care about more).
Hard to know how much extra risk this is in practice, though; that'd make a lovely study, if anyone can figure out how to measure it.
Minimizing packages Posted Jun 25, 2007 23:05 UTC (Mon) by flewellyn (subscriber, #5047) [Link] But the trade-off is that every box ends up running its own unique mix of code. Security-wise, this is good in that it increases diversity (so it's less likely someone will be able to pwn *all* Gentoo boxes), but reduces scrutiny on the actual code and interactions present on any particular box (so it's more likely that any particular Gentoo box *can* be pwned, which is probably what most sysadmins care about more). Actually, Gentoo does support binary packages, stored on a repository server that can be used to update the other machines in the cluster. I know of several clusters that do exactly this: one machine builds the updates, and then serves the binaries to the other machines. Obviously this really only works if you have a cluster of identical machines, but that's not unusual in a decent-sized server farm. Or a cluster of workstations.
Minimizing packages Posted Jun 26, 2007 4:01 UTC (Tue) by njs (guest, #40338) [Link] I know, but that's not very relevant to what I'm talking about. The issue I'm pointing out is that your particular set of programs each compiled with your particular quirky set of USE flags might have some novel security bug that no-one else noticed. Code that lots of people use tends to be well tested and highly scrutinized; weird and rarely used #ifdef'ed code tends to be just the opposite. This thread is advocating using more of the latter sort of code, and thus might actually increase security exposure. Running that same rarely used code across 10 boxes instead of 1 won't affect how much scrutiny it gets, you need lots of people in lots of different situations to get that.
It's hard to know whether this extra risk is important or just theoretical, though, hence my curiosity about quantifying it...
Minimizing packages Posted Jun 26, 2007 8:21 UTC (Tue) by flewellyn (subscriber, #5047) [Link] I can see how that might theoretically be a problem, but in all honesty, the set of USE flags for aparticular package doesn't have that much crazy variation.
In general, the USE flags tend to correspond to features that can be added or removed via
Setting weird compiler optimization flags in the global make.conf, now, there I can see a source
Minimizing packages Posted Jun 28, 2007 16:21 UTC (Thu) by jzbiciak (✭ supporter ✭, #5246) [Link] The point is that distro binaries very, very, very seldomly get rebuilt by the distro's users for most other distros. So, if one RHEL4 box is vulnerable in package XYZ due to how package XYZ was configured for RHEL4, then pretty much all RHEL4 users that have that package installed will have that vulnerability on their system.
In contrast, if the same package is available on Gentoo, and it's only vulnerable if you configure XYZ to make use of some other package PDQ, then only Gentoo users who have configured XYZ to use PDQ will be vulnerable. The same goes if you build a bunch of packages from source on any other distro, but only for those packages.
That's the distinction that's being drawn.
The flipside is that there might be some unforseen interaction between packages that a particular Gentoo configuration might expose and that other configurations won't. Since any given configuration will get less scrutiny, there's a higher chance of a given Gentoo box being vulnerable *on the basis of scrutiny alone*. The reality is that that's mostly theoretical, and in general removing features tends to (but does not always) remove vulnerabilities.
Minimizing packages Posted Jun 27, 2007 7:47 UTC (Wed) by HenrikH (guest, #31152) [Link] You are correct in that USE flags would yield a possibility that one runs programs with unknown holes in them, but then the attacker must also be aware of these unknown holes and also know that you compiled your packages with that very specific USE flags.
Not that it gives a warm and fuzzy feeling, but it would still be some uphill for a potential attacker. And more importantly is that thanks to the wide spread of USE flags a lot of previously unknown bugs will be reported (and hopefully fixed) due to the great variety of the users.
|
|||||||||||||