New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=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
|Bug assignment=Yes
|Packages=Yes
|IRC=#gentoo-hardened
|ParentProject=Project:Hardened
|PropagatesMembers=Yes
|LeadElectionDate=2019-08-27
|Members={{Project Member
|Developer=User:Blueness
|IsLead=Yes
}}{{Project Member
|Developer=User:Anarchy
|IsLead=No
}}{{Project Member
|Developer=User:Arkamar
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|Role=ppc64 helper
|IsLead=No
}}{{Project Member
|Developer=User:Sam
|IsLead=No
}}
}}
The musl project 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 libcs 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 libcs, 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] [https://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-musl/ stage3-amd64-musl-{hardened,vanilla}]
|-
| {{Keyword|arm}}
| armv7a-hardfp
| {{ Yes }}
| Development
| [https://gentoo.osuosl.org/releases/arm/autobuilds/ stage3-armv7a_hardfp-musl-{hardened,vanilla}]
|-
| {{Keyword|arm}}
| armv6j-hardfp
| {{ Yes }}
| Development
| [https://gentoo.osuosl.org/releases/arm/autobuilds/ stage3-armv6j_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
| {{ Yes }}
| Development
| [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc-musl-hardened-openrc stage3-ppc-musl-hardened-openrc]
|-
| {{Keyword|ppc64}}
| ppc64/ppc64le
| {{ Yes }}
| Development
| [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc64-musl-hardened-openrc stage3-ppc64-musl-hardened-openrc] / [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc64le-musl-hardened-openrc stage3-ppc64le-musl-hardened-openrc ]
|-
| {{Keyword|x86}}
| i686
| {{ Yes }}
| Development
| [https://distfiles.gentoo.org/releases/x86/autobuilds/current-stage3-i686-musl/ stage3-i686-musl]
|-
|}
== 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 musl project join the mailing list at {{Mail|gentoo-musl@lists.gentoo.org}} and visit our IRC channel at {{IRC|gentoo-hardened}} on Libera.Chat.
== See also ==
* {{See also|Project:Musl/Bluedragon}}
* {{See also|Musl_porting_notes|text=Musl porting n' |
Unified diff of changes made by edit (edit_diff) | '@@ -1,0 +1,132 @@
+{{Project
+|Name=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
+|Bug assignment=Yes
+|Packages=Yes
+|IRC=#gentoo-hardened
+|ParentProject=Project:Hardened
+|PropagatesMembers=Yes
+|LeadElectionDate=2019-08-27
+|Members={{Project Member
+|Developer=User:Blueness
+|IsLead=Yes
+}}{{Project Member
+|Developer=User:Anarchy
+|IsLead=No
+}}{{Project Member
+|Developer=User:Arkamar
+|IsLead=No
+}}{{Project Member
+|Developer=User:GYakovlev
+|Role=ppc64 helper
+|IsLead=No
+}}{{Project Member
+|Developer=User:Sam
+|IsLead=No
+}}
+}}
+The musl project 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 libcs 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 libcs, 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] [https://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-musl/ stage3-amd64-musl-{hardened,vanilla}]
+|-
+| {{Keyword|arm}}
+| armv7a-hardfp
+| {{ Yes }}
+| Development
+| [https://gentoo.osuosl.org/releases/arm/autobuilds/ stage3-armv7a_hardfp-musl-{hardened,vanilla}]
+|-
+| {{Keyword|arm}}
+| armv6j-hardfp
+| {{ Yes }}
+| Development
+| [https://gentoo.osuosl.org/releases/arm/autobuilds/ stage3-armv6j_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
+| {{ Yes }}
+| Development
+| [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc-musl-hardened-openrc stage3-ppc-musl-hardened-openrc]
+|-
+| {{Keyword|ppc64}}
+| ppc64/ppc64le
+| {{ Yes }}
+| Development
+| [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc64-musl-hardened-openrc stage3-ppc64-musl-hardened-openrc] / [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc64le-musl-hardened-openrc stage3-ppc64le-musl-hardened-openrc ]
+|-
+| {{Keyword|x86}}
+| i686
+| {{ Yes }}
+| Development
+| [https://distfiles.gentoo.org/releases/x86/autobuilds/current-stage3-i686-musl/ stage3-i686-musl]
+|-
+|}
+
+== 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 musl project join the mailing list at {{Mail|gentoo-musl@lists.gentoo.org}} and visit our IRC channel at {{IRC|gentoo-hardened}} on Libera.Chat.
+
+== See also ==
+
+* {{See also|Project:Musl/Bluedragon}}
+* {{See also|Musl_porting_notes|text=Musl porting n
' |
Lines added in edit (added_lines) | [
0 => '{{Project',
1 => '|Name=musl',
2 => '|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".',
3 => '|Email=musl@gentoo.org',
4 => '|Bug assignment=Yes',
5 => '|Packages=Yes',
6 => '|IRC=#gentoo-hardened',
7 => '|ParentProject=Project:Hardened',
8 => '|PropagatesMembers=Yes',
9 => '|LeadElectionDate=2019-08-27',
10 => '|Members={{Project Member',
11 => '|Developer=User:Blueness',
12 => '|IsLead=Yes',
13 => '}}{{Project Member',
14 => '|Developer=User:Anarchy',
15 => '|IsLead=No',
16 => '}}{{Project Member',
17 => '|Developer=User:Arkamar',
18 => '|IsLead=No',
19 => '}}{{Project Member',
20 => '|Developer=User:GYakovlev',
21 => '|Role=ppc64 helper',
22 => '|IsLead=No',
23 => '}}{{Project Member',
24 => '|Developer=User:Sam',
25 => '|IsLead=No',
26 => '}}',
27 => '}}',
28 => 'The musl project 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.',
29 => '',
30 => '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.',
31 => '',
32 => 'For embedded systems, the size and speed of your libc become important issues which are better addressed by libcs 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.',
33 => '',
34 => '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.',
35 => '',
36 => 'Since there are different needs for different folks, in Gentoo we are not afraid to target ''anything'' and ''everything'': all arches, all libcs, hardened/vanilla userland, hardened/vanilla Linux kernel, and even different kernels.',
37 => '',
38 => '[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: ',
39 => '',
40 => '* 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.',
41 => '* Position Independent Execution ([[wikipedia:Position-independent_code|PIE]]).',
42 => '* Bind now and relro, linker hardening to protect the global offset table.',
43 => '',
44 => '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]). ',
45 => '',
46 => '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.',
47 => '',
48 => '== Goals ==',
49 => '',
50 => 'The project goals can be best summarized by the following chart: ',
51 => '',
52 => '{| class="table table-condensed table-striped" style="text-align: left;" ',
53 => '|- ',
54 => '! Arch',
55 => '! Subarchs',
56 => '! Tool Chain Hardening',
57 => '! Status',
58 => '! Downloads',
59 => '|- ',
60 => '| {{Keyword|amd64}}',
61 => '| Generic',
62 => '| {{ Yes }}',
63 => '| Development',
64 => '| [http://releases.freeharbor.net Desktop] [https://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-musl/ stage3-amd64-musl-{hardened,vanilla}]',
65 => '|- ',
66 => '| {{Keyword|arm}}',
67 => '| armv7a-hardfp',
68 => '| {{ Yes }}',
69 => '| Development',
70 => '| [https://gentoo.osuosl.org/releases/arm/autobuilds/ stage3-armv7a_hardfp-musl-{hardened,vanilla}]',
71 => '|- ',
72 => '| {{Keyword|arm}}',
73 => '| armv6j-hardfp',
74 => '| {{ Yes }}',
75 => '| Development',
76 => '| [https://gentoo.osuosl.org/releases/arm/autobuilds/ stage3-armv6j_hardfp-musl-{hardened,vanilla}]',
77 => '|- ',
78 => '| {{Keyword|mips}}',
79 => '| mips32r2',
80 => '| {{ No }}',
81 => '| NA',
82 => '| Not Yet',
83 => '|- ',
84 => '| {{Keyword|mips}}',
85 => '| mipsel3',
86 => '| {{ No }}',
87 => '| Development',
88 => '| [http://distfiles.gentoo.org/experimental/mips/musl stage3-mipsel3-musl-vanilla]',
89 => '|- ',
90 => '| {{Keyword|ppc}}',
91 => '| classic',
92 => '| {{ Yes }}',
93 => '| Development',
94 => '| [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc-musl-hardened-openrc stage3-ppc-musl-hardened-openrc]',
95 => '|- ',
96 => '| {{Keyword|ppc64}}',
97 => '| ppc64/ppc64le',
98 => '| {{ Yes }}',
99 => '| Development',
100 => '| [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc64-musl-hardened-openrc stage3-ppc64-musl-hardened-openrc] / [https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc64le-musl-hardened-openrc stage3-ppc64le-musl-hardened-openrc ]',
101 => '|- ',
102 => '| {{Keyword|x86}}',
103 => '| i686',
104 => '| {{ Yes }}',
105 => '| Development',
106 => '| [https://distfiles.gentoo.org/releases/x86/autobuilds/current-stage3-i686-musl/ stage3-i686-musl]',
107 => '|-',
108 => '|}',
109 => '',
110 => '== Contributors ==',
111 => '',
112 => 'The following people are or have contributed to the project:',
113 => '',
114 => '{| class="table table-condensed table-striped" style="text-align: left;" ',
115 => '! Contributor',
116 => '! Email',
117 => '! Still active?',
118 => '|- ',
119 => '| Felix Janda',
120 => '| felix.janda@posteo.de',
121 => '| {{ Yes }}',
122 => '|}',
123 => '',
124 => '== Participation ==',
125 => '',
126 => 'To participate in the musl project join the mailing list at {{Mail|gentoo-musl@lists.gentoo.org}} and visit our IRC channel at {{IRC|gentoo-hardened}} on Libera.Chat.',
127 => '',
128 => '== See also ==',
129 => '',
130 => '* {{See also|Project:Musl/Bluedragon}}',
131 => '* {{See also|Musl_porting_notes|text=Musl porting n'
] |
New page text, stripped of any markup (new_text) | '
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".
Project email
musl@gentoo.org
Packages
p.g.o/musl@gentoo.org
IRC channel
#gentoo-hardened (webchat)
Bugs
Related bugs
Lead(s)
none Last elected: 2019-08-27
Member(s)
Subproject(s)(and inherited member(s))
(none)
Parent Project
Hardened
Project listing
The musl project has a goal similar to its sister subproject, Hardened uClibc, but with the intention of using musl to replace 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 libcs designed with that purpose in mind. 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. 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 uClibc, it is not configurable. How glibc, uClibc and musl compare on the various points of interest is complex and something that will probably be debated forever.
The musl team does provide a 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 libcs, hardened/vanilla userland, hardened/vanilla Linux kernel, and even different kernels.
musl's completeness, including a robust implementation of POSIX threads, means that we can include all of Gentoo's Hardened toolchain goodies without any problems:
Stack Smashing Protection (SSP), which requires threads but doesn't work with the old NPTL or LinuxThreads that uClibc provides.
Position Independent Execution (PIE).
Bind now and relro, linker hardening to protect the global offset table.
These are augmented by the kernel hardening, especially PaX's enhanced address space layout randomization (ASLR).
This subproject aims to treat musl more as a drop in alternative to 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 musl compatible.
Contents
1 Goals
2 Contributors
3 Participation
4 See also
Goals[edit | edit source]
The project goals can be best summarized by the following chart:
Arch
Subarchs
Tool Chain Hardening
Status
Downloads
amd64
Generic
Yes
Development
Desktop stage3-amd64-musl-{hardened,vanilla}
arm
armv7a-hardfp
Yes
Development
stage3-armv7a_hardfp-musl-{hardened,vanilla}
arm
armv6j-hardfp
Yes
Development
stage3-armv6j_hardfp-musl-{hardened,vanilla}
mips
mips32r2
No
NA
Not Yet
mips
mipsel3
No
Development
stage3-mipsel3-musl-vanilla
ppc
classic
Yes
Development
stage3-ppc-musl-hardened-openrc
ppc64
ppc64/ppc64le
Yes
Development
stage3-ppc64-musl-hardened-openrc / stage3-ppc64le-musl-hardened-openrc
x86
i686
Yes
Development
stage3-i686-musl
Contributors[edit | edit source]
The following people are or have contributed to the project:
Contributor
Email
Still active?
Felix Janda
felix.janda@posteo.de
Yes
Participation[edit | edit source]
To participate in the musl project join the mailing list at gentoo-musl@lists.gentoo.org and visit our IRC channel at #gentoo-hardened (webchat) on Libera.Chat.
See also[edit | edit source]
Project:Musl/Bluedragon — covers using a hardened musl XFCE desktop
{{See also|Musl_porting_notes|text=Musl porting n' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tbody><tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>musl</big>
</th></tr>
<tr valign="top">
<th>Description
</th>
<td style="text-align: justify;">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".
</td></tr>
<tr>
<th><span title="Mails to member(s) listed below.">Project email</span>
</th>
<td><a rel="nofollow" class="external text" href="mailto:musl@gentoo.org">musl@gentoo.org</a>
</td></tr>
<tr>
<th><span title="Link to packages.g.o for ebuilds maintained in gentoo.git.">Packages</span>
</th>
<td><span class="fa fa-cubes fa-fw"></span> <a rel="nofollow" class="external text" href="https://packages.gentoo.org/maintainer/musl@gentoo.org">p.g.o/musl@gentoo.org</a>
<p><br />
</p>
</td></tr>
<tr>
<th><span title="The link opens an IRC client to libera.chat IRC channel.">IRC channel</span>
</th>
<td><span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-hardened">#gentoo-hardened</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-hardened">webchat</a></span>)
</td></tr>
<tr>
<th><span title="The link opens to a bugs.gentoo.org search based on the projects email address.">Bugs</span>
</th>
<td><span class="fa fa-bug fa-fw"></span> <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=PLEASETEST&bug_status=IN_PROGRESS&email1=musl@gentoo.org&emailassigned_to1=1&order=bug_id%20DESC">Related bugs</a>
</td></tr>
<tr valign="top">
<th>Lead(s)
</th>
<td>none <br />Last elected: 2019-08-27
</td></tr>
<tr valign="top">
<th>Member(s)
</th>
<td>
</td></tr>
<tr valign="top">
<th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td>(none)
</td></tr>
<tr>
<th>Parent Project
</th>
<td><a href="/wiki/Project:Hardened" title="Project:Hardened">Hardened</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></tbody></table>
<p>The musl project has a goal similar to its sister subproject, <a href="/wiki/Project:Hardened_uClibc" title="Project:Hardened uClibc">Hardened uClibc</a>, but with the intention of using <a rel="nofollow" class="external text" href="http://www.musl-libc.org/">musl</a> to replace <a rel="nofollow" class="external text" href="http://www.gnu.org/software/libc/">glibc</a> as the system's "standard C library" or "libc" for short.
</p><p>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.
</p><p>For embedded systems, the size and speed of your libc become important issues which are better addressed by libcs designed with that purpose in mind. <a rel="nofollow" class="external text" href="http://www.uclibc.org/">uClibc</a> 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. <a rel="nofollow" class="external text" href="http://www.musl-libc.org/">musl</a> 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 <a rel="nofollow" class="external text" href="http://www.uclibc.org/">uClibc</a>, it is not configurable. How <a rel="nofollow" class="external text" href="http://www.gnu.org/software/libc/">glibc</a>, <a rel="nofollow" class="external text" href="http://www.uclibc.org/">uClibc</a> and <a rel="nofollow" class="external text" href="http://www.musl-libc.org/">musl</a> compare on the various points of interest is complex and something that will probably be debated forever.
</p><p>The musl team does provide a <a rel="nofollow" class="external text" href="http://www.etalabs.net/compare_libcs.html">table of C/POSIX standard library implementations for Linux</a> that you can browse.
</p><p>Since there are different needs for different folks, in Gentoo we are not afraid to target <i>anything</i> and <i>everything</i>: all arches, all libcs, hardened/vanilla userland, hardened/vanilla Linux kernel, and even different kernels.
</p><p><a rel="nofollow" class="external text" href="http://www.musl-libc.org/">musl</a>'s completeness, including a robust implementation of <a rel="nofollow" class="external text" href="https://en.wikipedia.org/wiki/POSIX_Threads">POSIX threads</a>, means that we can include all of Gentoo's Hardened toolchain goodies without any problems:
</p>
<ul><li>Stack Smashing Protection (<a href="https://en.wikipedia.org/wiki/Buffer_overflow_protection" class="extiw" title="wikipedia:Buffer overflow protection">SSP</a>), which requires threads but doesn't work with the old <a href="https://en.wikipedia.org/wiki/Native_POSIX_Thread_Library" class="extiw" title="wikipedia:Native POSIX Thread Library">NPTL</a> or <a href="https://en.wikipedia.org/wiki/LinuxThreads" class="extiw" title="wikipedia:LinuxThreads">LinuxThreads</a> that uClibc provides.</li>
<li>Position Independent Execution (<a href="https://en.wikipedia.org/wiki/Position-independent_code" class="extiw" title="wikipedia:Position-independent code">PIE</a>).</li>
<li>Bind now and relro, linker hardening to protect the global offset table.</li></ul>
<p>These are augmented by the kernel hardening, especially <a rel="nofollow" class="external text" href="https://pax.grsecurity.net/">PaX</a>'s enhanced address space layout randomization (<a rel="nofollow" class="external text" href="https://pax.grsecurity.net/docs/aslr.txt">ASLR</a>).
</p><p>This subproject aims to treat <a rel="nofollow" class="external text" href="http://www.musl-libc.org/">musl</a> more as a drop in alternative to <a rel="nofollow" class="external text" href="http://www.gnu.org/software/libc/">glibc</a>, 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 <a rel="nofollow" class="external text" href="http://www.musl-libc.org/">musl</a> compatible.
</p>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Goals"><span class="tocnumber">1</span> <span class="toctext">Goals</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Contributors"><span class="tocnumber">2</span> <span class="toctext">Contributors</span></a></li>
<li class="toclevel-1 tocsection-3"><a href="#Participation"><span class="tocnumber">3</span> <span class="toctext">Participation</span></a></li>
<li class="toclevel-1 tocsection-4"><a href="#See_also"><span class="tocnumber">4</span> <span class="toctext">See also</span></a></li>
</ul>
</div>
<h2><span class="mw-headline" id="Goals">Goals</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=User:Immolo/musl-ng&veaction=edit&section=1" class="mw-editsection-visualeditor" title="Edit section: Goals">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=User:Immolo/musl-ng&action=edit&section=1" title="Edit section: Goals">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>The project goals can be best summarized by the following chart:
</p>
<table class="table table-condensed table-striped" style="text-align: left;">
<tbody><tr>
<th>Arch
</th>
<th>Subarchs
</th>
<th>Tool Chain Hardening
</th>
<th>Status
</th>
<th>Downloads
</th></tr>
<tr>
<td><b><span style="font-family: monospace; font-size: 95%; color: #54487a">amd64</span></b>
</td>
<td>Generic
</td>
<td style="background-color: #DFF0D8; color: black; vertical-align: middle; text-align: left;" class="cell-yes"><i class="fa fa-check"></i> Yes
</td>
<td>Development
</td>
<td><a rel="nofollow" class="external text" href="http://releases.freeharbor.net">Desktop</a> <a rel="nofollow" class="external text" href="https://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-musl/">stage3-amd64-musl-{hardened,vanilla}</a>
</td></tr>
<tr>
<td><b><span style="font-family: monospace; font-size: 95%; color: #54487a">arm</span></b>
</td>
<td>armv7a-hardfp
</td>
<td style="background-color: #DFF0D8; color: black; vertical-align: middle; text-align: left;" class="cell-yes"><i class="fa fa-check"></i> Yes
</td>
<td>Development
</td>
<td><a rel="nofollow" class="external text" href="https://gentoo.osuosl.org/releases/arm/autobuilds/">stage3-armv7a_hardfp-musl-{hardened,vanilla}</a>
</td></tr>
<tr>
<td><b><span style="font-family: monospace; font-size: 95%; color: #54487a">arm</span></b>
</td>
<td>armv6j-hardfp
</td>
<td style="background-color: #DFF0D8; color: black; vertical-align: middle; text-align: left;" class="cell-yes"><i class="fa fa-check"></i> Yes
</td>
<td>Development
</td>
<td><a rel="nofollow" class="external text" href="https://gentoo.osuosl.org/releases/arm/autobuilds/">stage3-armv6j_hardfp-musl-{hardened,vanilla}</a>
</td></tr>
<tr>
<td><b><span style="font-family: monospace; font-size: 95%; color: #54487a">mips</span></b>
</td>
<td>mips32r2
</td>
<td style="background-color: #F2DEDE; color: black; vertical-align: middle; text-align: left;" class="cell-no"><i class="fa fa-times"></i> No
</td>
<td>NA
</td>
<td>Not Yet
</td></tr>
<tr>
<td><b><span style="font-family: monospace; font-size: 95%; color: #54487a">mips</span></b>
</td>
<td>mipsel3
</td>
<td style="background-color: #F2DEDE; color: black; vertical-align: middle; text-align: left;" class="cell-no"><i class="fa fa-times"></i> No
</td>
<td>Development
</td>
<td><a rel="nofollow" class="external text" href="http://distfiles.gentoo.org/experimental/mips/musl">stage3-mipsel3-musl-vanilla</a>
</td></tr>
<tr>
<td><b><span style="font-family: monospace; font-size: 95%; color: #54487a">ppc</span></b>
</td>
<td>classic
</td>
<td style="background-color: #DFF0D8; color: black; vertical-align: middle; text-align: left;" class="cell-yes"><i class="fa fa-check"></i> Yes
</td>
<td>Development
</td>
<td><a rel="nofollow" class="external text" href="https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc-musl-hardened-openrc">stage3-ppc-musl-hardened-openrc</a>
</td></tr>
<tr>
<td><b><span style="font-family: monospace; font-size: 95%; color: #54487a">ppc64</span></b>
</td>
<td>ppc64/ppc64le
</td>
<td style="background-color: #DFF0D8; color: black; vertical-align: middle; text-align: left;" class="cell-yes"><i class="fa fa-check"></i> Yes
</td>
<td>Development
</td>
<td><a rel="nofollow" class="external text" href="https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc64-musl-hardened-openrc">stage3-ppc64-musl-hardened-openrc</a> / <a rel="nofollow" class="external text" href="https://distfiles.gentoo.org/releases/ppc/autobuilds/current-stage3-ppc64le-musl-hardened-openrc">stage3-ppc64le-musl-hardened-openrc </a>
</td></tr>
<tr>
<td><b><span style="font-family: monospace; font-size: 95%; color: #54487a">x86</span></b>
</td>
<td>i686
</td>
<td style="background-color: #DFF0D8; color: black; vertical-align: middle; text-align: left;" class="cell-yes"><i class="fa fa-check"></i> Yes
</td>
<td>Development
</td>
<td><a rel="nofollow" class="external text" href="https://distfiles.gentoo.org/releases/x86/autobuilds/current-stage3-i686-musl/">stage3-i686-musl</a>
</td></tr>
</tbody></table>
<h2><span class="mw-headline" id="Contributors">Contributors</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=User:Immolo/musl-ng&veaction=edit&section=2" class="mw-editsection-visualeditor" title="Edit section: Contributors">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=User:Immolo/musl-ng&action=edit&section=2" title="Edit section: Contributors">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>The following people are or have contributed to the project:
</p>
<table class="table table-condensed table-striped" style="text-align: left;">
<tbody><tr>
<th>Contributor
</th>
<th>Email
</th>
<th>Still active?
</th></tr>
<tr>
<td>Felix Janda
</td>
<td>felix.janda@posteo.de
</td>
<td style="background-color: #DFF0D8; color: black; vertical-align: middle; text-align: left;" class="cell-yes"><i class="fa fa-check"></i> Yes
</td></tr></tbody></table>
<h2><span class="mw-headline" id="Participation">Participation</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=User:Immolo/musl-ng&veaction=edit&section=3" class="mw-editsection-visualeditor" title="Edit section: Participation">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=User:Immolo/musl-ng&action=edit&section=3" title="Edit section: Participation">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>To participate in the musl project join the mailing list at <a rel="nofollow" class="external text" href="mailto:gentoo-musl@lists.gentoo.org">gentoo-musl@lists.gentoo.org</a> and visit our IRC channel at <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-hardened">#gentoo-hardened</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-hardened">webchat</a></span>) on Libera.Chat.
</p>
<h2><span class="mw-headline" id="See_also">See also</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=User:Immolo/musl-ng&veaction=edit&section=4" class="mw-editsection-visualeditor" title="Edit section: See also">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=User:Immolo/musl-ng&action=edit&section=4" title="Edit section: See also">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul><li><a href="/wiki/Project:Musl/Bluedragon" title="Project:Musl/Bluedragon">Project:Musl/Bluedragon</a> — covers using a hardened musl XFCE desktop</li>
<li>{{See also|Musl_porting_notes|text=Musl porting n</li></ul>
' |
Wiki