3 ms·

The corollary being that you don't need to worry about breaking things when upgrading libc

• gpm 8y ago
  Well sure, but at least for networked services (which is unfortunately a substantial fraction of the binaries on my computer) I'd happily take the security over functionality tradeoff. If things don't work, I notice and fix it. If things aren't secure, I don't notice, get hacked, and my files get ransomed back to me.
  • zaarn 8y ago
    You could have both, in theory. Ie, use static linking unless a compatible version of the library is present on disk with a higher version number at runtime.
    • AnIdiotOnTheNet 8y ago
      That won't prevent the higher version from breaking your application.
      • zaarn 8y ago
        In theory it could, simply remove the newer version and the app uses it's internal library again. Or alternatively, like LD_PRELOAD, just have an env variable; LD_DONT_PRELOAD. Though that would make it more complicated.