Abuse filter log

'{{Project |Name=Hardened musl |Description=This subproject aims to port the hardened tool chain to musl based systems for a variety of architectures. The project treats musl as an alternative to glibc and uClibc, and not necessarily as "embedded". |Email=musl@gentoo.org |IRC=#gentoo-hardened |ParentProject=Project:Hardened |PropagatesMembers=No |LeadElectionDate=2019/08/27 |Members={{Project Member |Developer=User:Blueness |Role=Developer |IsLead=Yes }}{{Project Member |Developer=User:Anarchy |Role=Developer |IsLead=No }} }} The Hardened musl subproject has a goal similar to its sister subproject, [[Project:Hardened_uClibc|Hardened uClibc]], but with the intention of using [http://www.musl-libc.org/ musl] to replace [http://www.gnu.org/software/libc/ glibc] as the system's "standard C library," or "libc" for short. A system's libc forms an integral part of the toolchain, but unlike the other components, it remains a runtime dependency of nearly every dynamically linked object in the system, or becomes incorporated into statically linked executables. For embedded systems, the size and speed of your libc become important issues which are better addressed by libc's designed with that purpose in mind. [http://www.uclibc.org/ uClibc] addresses at least the size issue by being very configurable, so any unneeded code can be turned off. Whether a function is required by POSIX standards or not doesn't matter if you are not using it for some targetted application. [http://www.musl-libc.org/ musl] takes a different approach: it is written with static linking in mind, but also with fast dynamic linking capabilities, while remaining close to standards and conscious of security issues. However, unlike [http://www.uclibc.org/ uClibc], it is not configurable. How [http://www.gnu.org/software/libc/ glibc], [http://www.uclibc.org/ uClibc] and [http://www.musl-libc.org/ musl] compare on the various points of interest is complex and something that will probably be debated forever. The musl team does provide a [http://www.etalabs.net/compare_libcs.html table of C/POSIX standard library implementations for Linux] that you can browse. Since there are different needs for different folks, in Gentoo we are not afraid to target ''anything'' and ''everything'': all arches, all libc's, hardened/vanilla userland, hardened/vanilla Linux kernel, and even different kernels. [http://www.musl-libc.org/ musl]'s completeness, including a robust implementation of [https://en.wikipedia.org/wiki/POSIX_Threads POSIX threads], means that we can include all of Gentoo's Hardened toolchain goodies without any problems: * Stack Smashing Protection ([[wikipedia:Buffer_overflow_protection|SSP]]), which requires threads but doesn't work with the old [[wikipedia:Native_POSIX_Thread_Library|NPTL]] or [[wikipedia:LinuxThreads|LinuxThreads]] that uClibc provides. * Position Independent Execution ([[wikipedia:Position-independent_code|PIE]]). * Bind now and relro, linker hardening to protect the global offset table. These are augmented by the kernel hardening, especially [http://pax.grsecurity.net/ PaX]'s enhanced address space layout randomization ([http://pax.grsecurity.net/docs/aslr.txt ASLR]). This subproject aims to treat [http://www.musl-libc.org/ musl] more as a drop in alternative to [http://www.gnu.org/software/libc/ glibc], and not necessarily as "embedded". This is not at the exclusion of the concerns of embedded systems, but rather to make our userland tarballs as flexible as possible. They can be used as development environments for native compiling on native hardware, starting points to build server or desktop systems, or they can be stripped down to just the essential apps for whatever purpose. The stages are not "embedded" in the sense that they use busybox as their "Swiss Army Knife" of common UNIX utilities. While not excluding this possibility, we aim at making most (all?) of Gentoo's packages both hardened and [http://www.musl-libc.org/ musl] compatible. == Goals == The project goals can be best summarized by the following chart: {| class="table table-condensed table-striped" style="text-align: left;" |- ! Arch ! Subarchs ! Tool Chain Hardening ! Status ! Downloads |- | {{Keyword|amd64}} | Generic | {{ Yes }} | Development | [http://releases.freeharbor.net Desktop] [http://distfiles.gentoo.org/experimental/amd64/musl/ stage3-amd64-musl-{hardened,vanilla}] |- | {{Keyword|arm}} | armv7a-hardfp | {{ Yes }} | Development | [http://distfiles.gentoo.org/experimental/arm/musl/ stage3-armv7a_hardfp-musl-{hardened,vanilla}] |- | {{Keyword|mips}} | mips32r2 | {{ No }} | NA | Not Yet |- | {{Keyword|mips}} | mipsel3 | {{ No }} | Development | [http://distfiles.gentoo.org/experimental/mips/musl stage3-mipsel3-musl-vanilla] |- | {{Keyword|ppc}} | classic | {{ No }} | Development | [http://distfiles.gentoo.org/experimental/ppc/musl/ stage3-ppc-musl-vanilla] |- | {{Keyword|x86}} | i686 | {{ No }} | Development | [http://distfiles.gentoo.org/experimental/x86/musl/ stage3-i686-musl-vanilla] |- |} == Working with musl == Unlike the situation with uClibc, where pretty much every package in the Gentoo portage tree "just builds," musl's adherence to standards means that many packages which deviate from those standards, primarily [[wikipedia:POSIX|POSIX]], need some patching. Most of this is minor, like the location of header files, but some is more substantial. So we maintain the [https://gitweb.gentoo.org/proj/musl.git musl] overlay to house those patches, and this overlay must be added to the stage3's to be able to update and maintain them. Here's how: 0) Get your chroot ready as you would on any other stage3. See the [[Handbook]]. 1) Set up your favorite <var>GENTOO_MIRRORS</var> and sync-uri and sync the main ebuild repository. Obviously replace 192.168.3.1 with your servers of choice: {{RootCmd |echo GENTOO_MIRRORS{{=}}<nowiki>ftp://192.168.3.1/pub/gentoo</nowiki> >> /etc/portage/make.conf |sed -i "/^sync-uri/d" /etc/portage/repos.conf/gentoo.conf |echo "sync-uri {{=}} rsync://192.168.3.1/portage" >> /etc/portage/repos.conf/gentoo.conf |emerge --sync }} 2) Set up the nameserver for DNS resolution: {{RootCmd|echo nameserver 192.168.3.1 >> /etc/resolv.conf}} 3) We need to get git in order to add the overlay. Unfortunately, right now we can't build git with gnupg support: {{RootCmd|echo "dev-vcs/git -gpg" >> /etc/portage/package.use }} {{Emerge|app-portage/layman dev-vcs/git}} 4) Let's add the overlay. {{RootCmd |layman -L |layman -a musl }} 5) Okay now we can update. If we tried to update without the overlay, we get a bunch of downgrades to ebuilds that are slightly broken on musl and will not build. {{RootCmd|emerge -uvNDq @world}} 6) In the future, update both the portage tree and the overlay before repeating step 5. {{RootCmd |emerge --sync |layman -S |emerge -uvNDq @world }} == Contributors == The following people are or have contributed to the project: {| class="table table-condensed table-striped" style="text-align: left;" ! Contributor ! Email ! Still active? |- | Felix Janda | felix.janda@posteo.de | {{ Yes }} |} == Participation == To participate in the Hardened musl project join the mailing list at {{Mail|gentoo-musl@lists.gentoo.org}} and visit our IRC channel at {{IRC|gentoo-hardened}} on Freenode. == See also == * [[Project:Hardened_musl/Bluedragon|Bluedragon]] - A hardened musl XFCE desktop.'