Re: linking statically against dietlibc: a blocker?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Enrico Scholz wrote:
paul@xxxxxxxxxxxxx (Paul Wouters) writes:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176579
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176581
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176582
...
But I don't think we should start using different c libraries for
random binaries.

Tickets above are not for "random binaries" but for projects which are
designed for dietlibc. Using glibc for them would make binaries larger,
slower and increases memory usage without providing a single gain.


You lose the benefit of FORTIFY_SOURCE and address randomization of entry points of libc functions, both of which are detriments to security.

Warren Togami
wtogami@xxxxxxxxxx

--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list

[Index of Archives]     [Fedora General Discussion]     [Fedora Art]     [Fedora Docs]     [Fedora Package Review]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite Backpacking]     [KDE Users]

  Powered by Linux