home.social

#musl — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #musl, aggregated by home.social.

  1. Do you use @nodejs on @alpinelinux? While the Node.js project publishes Alpine containers to dockerhub it is currently an "experimental" platform and does not have the same guarantees as other platforms.

    We are looking for volunteers to help us bring Alpine to "Tier 2" where it would be built and released through the normal CI process.

    If you can help and/or work for a company depending on Node on Alpine/musl then let us know at github.com/nodejs/node/issues/

  2. Do you use @nodejs on @alpinelinux? While the Node.js project publishes Alpine containers to dockerhub it is currently an "experimental" platform and does not have the same guarantees as other platforms.

    We are looking for volunteers to help us bring Alpine to "Tier 2" where it would be built and released through the normal CI process.

    If you can help and/or work for a company depending on Node on Alpine/musl then let us know at github.com/nodejs/node/issues/
    #alpine #musl #nodejs #OpenSource

  3. Do you use @nodejs on @alpinelinux? While the Node.js project publishes Alpine containers to dockerhub it is currently an "experimental" platform and does not have the same guarantees as other platforms.

    We are looking for volunteers to help us bring Alpine to "Tier 2" where it would be built and released through the normal CI process.

    If you can help and/or work for a company depending on Node on Alpine/musl then let us know at github.com/nodejs/node/issues/
    #alpine #musl #nodejs #OpenSource

  4. Do you use @nodejs on @alpinelinux? While the Node.js project publishes Alpine containers to dockerhub it is currently an "experimental" platform and does not have the same guarantees as other platforms.

    We are looking for volunteers to help us bring Alpine to "Tier 2" where it would be built and released through the normal CI process.

    If you can help and/or work for a company depending on Node on Alpine/musl then let us know at github.com/nodejs/node/issues/
    #alpine #musl #nodejs #OpenSource

  5. This exploit write-up features #musl 1.1.24, whose oldmalloc (dlmalloc-like) was used to convert the exploitable bug in the application into an arbitrary write primitive.

    synacktiv.com/en/publications/

    musl 1.2.1 or later, with mallocng, would probably have rendered this non-exploitable or would have at least required non-malloc-based approaches to exploiting the initial application bug.

  6. This exploit write-up features #musl 1.1.24, whose oldmalloc (dlmalloc-like) was used to convert the exploitable bug in the application into an arbitrary write primitive.

    synacktiv.com/en/publications/

    musl 1.2.1 or later, with mallocng, would probably have rendered this non-exploitable or would have at least required non-malloc-based approaches to exploiting the initial application bug.

  7. This exploit write-up features 1.1.24, whose oldmalloc (dlmalloc-like) was used to convert the exploitable bug in the application into an arbitrary write primitive.

    synacktiv.com/en/publications/

    musl 1.2.1 or later, with mallocng, would probably have rendered this non-exploitable or would have at least required non-malloc-based approaches to exploiting the initial application bug.

  8. This exploit write-up features #musl 1.1.24, whose oldmalloc (dlmalloc-like) was used to convert the exploitable bug in the application into an arbitrary write primitive.

    synacktiv.com/en/publications/

    musl 1.2.1 or later, with mallocng, would probably have rendered this non-exploitable or would have at least required non-malloc-based approaches to exploiting the initial application bug.

  9. This exploit write-up features #musl 1.1.24, whose oldmalloc (dlmalloc-like) was used to convert the exploitable bug in the application into an arbitrary write primitive.

    synacktiv.com/en/publications/

    musl 1.2.1 or later, with mallocng, would probably have rendered this non-exploitable or would have at least required non-malloc-based approaches to exploiting the initial application bug.

  10. Does #musl have a counterpart to glibc gai.conf? I want to prefer my ULA IPv6 /48 prefix over global addresses, if the device has an address within the prefix. ​:neocat_think:​

  11. Does #musl have a counterpart to glibc gai.conf? I want to prefer my ULA IPv6 /48 prefix over global addresses, if the device has an address within the prefix. ​:neocat_think:​

  12. Does #musl have a counterpart to glibc gai.conf? I want to prefer my ULA IPv6 /48 prefix over global addresses, if the device has an address within the prefix. ​:neocat_think:​

  13. Does #musl have a counterpart to glibc gai.conf? I want to prefer my ULA IPv6 /48 prefix over global addresses, if the device has an address within the prefix. ​:neocat_think:​

  14. Does #musl have a counterpart to glibc gai.conf? I want to prefer my ULA IPv6 /48 prefix over global addresses, if the device has an address within the prefix. ​:neocat_think:​

  15. My #emulator takes a ROM filename on the #CommandLine, among other options. I use the #musl library's #getopt to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python. youtu.be/PAw478XJYWI #FamilySizeVM #emudev #CLI #timelapse #emulator

    Parsing a command line in C is...

  16. My #emulator takes a ROM filename on the #CommandLine, among other options. I use the #musl library's #getopt to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python. youtu.be/PAw478XJYWI #FamilySizeVM #emudev #CLI #timelapse #emulator

    Parsing a command line in C is...

  17. My #emulator takes a ROM filename on the #CommandLine, among other options. I use the #musl library's #getopt to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python. youtu.be/PAw478XJYWI #FamilySizeVM #emudev #CLI #timelapse #emulator

    Parsing a command line in C is...

  18. My #emulator takes a ROM filename on the #CommandLine, among other options. I use the #musl library's #getopt to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python. youtu.be/PAw478XJYWI #FamilySizeVM #emudev #CLI #timelapse #emulator

    Parsing a command line in C is...

  19. My emulator takes a path to a ROM image on the command line, among other options. I use the musl library's getopt_long function to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python.
    youtu.be/PAw478XJYWI

    #FamilySizeVM #emudev #NESdev #CommandLine #CLI #musl #getopt #timelapse #emulator

  20. My emulator takes a path to a ROM image on the command line, among other options. I use the musl library's getopt_long function to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python.
    youtu.be/PAw478XJYWI

    #FamilySizeVM #emudev #NESdev #CommandLine #CLI #musl #getopt #timelapse #emulator

  21. My emulator takes a path to a ROM image on the command line, among other options. I use the musl library's getopt_long function to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python.
    youtu.be/PAw478XJYWI

    #FamilySizeVM #emudev #NESdev #CommandLine #CLI #musl #getopt #timelapse #emulator

  22. My emulator takes a path to a ROM image on the command line, among other options. I use the musl library's getopt_long function to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python.
    youtu.be/PAw478XJYWI

    #FamilySizeVM #emudev #NESdev #CommandLine #CLI #musl #getopt #timelapse #emulator

  23. My emulator takes a path to a ROM image on the command line, among other options. I use the musl library's getopt_long function to parse the command in C. It makes me appreciate the libraries that come with newer languages like Python.
    youtu.be/PAw478XJYWI

    #FamilySizeVM #emudev #NESdev #CommandLine #CLI #musl #getopt #timelapse #emulator

  24. Chimera Linux does things differently: the distro is built from scratch, musl instead of glibc, init is dinit, FreeBSD userland, ...

    Fresh install on my Thinkpad using OpenZFS and ZFSBootMenu. Curious to explore further. I'm thinking of a setup where Chimera is my desktop and FreeBSD on a home server.

    #ChimeraLinux #musl #dinit #FreeBSD #ZFS #ZFSBootMenu

  25. Chimera Linux does things differently: the distro is built from scratch, musl instead of glibc, init is dinit, FreeBSD userland, ...

    Fresh install on my Thinkpad using OpenZFS and ZFSBootMenu. Curious to explore further. I'm thinking of a setup where Chimera is my desktop and FreeBSD on a home server.

  26. Chimera Linux does things differently: the distro is built from scratch, musl instead of glibc, init is dinit, FreeBSD userland, ...

    Fresh install on my Thinkpad using OpenZFS and ZFSBootMenu. Curious to explore further. I'm thinking of a setup where Chimera is my desktop and FreeBSD on a home server.

    #ChimeraLinux #musl #dinit #FreeBSD #ZFS #ZFSBootMenu

  27. Chimera Linux does things differently: the distro is built from scratch, musl instead of glibc, init is dinit, FreeBSD userland, ...

    Fresh install on my Thinkpad using OpenZFS and ZFSBootMenu. Curious to explore further. I'm thinking of a setup where Chimera is my desktop and FreeBSD on a home server.

    #ChimeraLinux #musl #dinit #FreeBSD #ZFS #ZFSBootMenu

  28. Chimera Linux does things differently: the distro is built from scratch, musl instead of glibc, init is dinit, FreeBSD userland, ...

    Fresh install on my Thinkpad using OpenZFS and ZFSBootMenu. Curious to explore further. I'm thinking of a setup where Chimera is my desktop and FreeBSD on a home server.

    #ChimeraLinux #musl #dinit #FreeBSD #ZFS #ZFSBootMenu

  29. Came across this again while reviewing some code in #musl iconv: the standard legacy encoding for Korean, EUC-KR/CP949, is grossly underdocumented. Unlike a most other CJK encodings, Wikipedia has basically no information on the actual encoding structure, and WHATWG chooses to specify it as an arbitrary table completely disregarding the structure.

    So, a little thread on it, so it's written down somewhere. Maybe someday someone will write a proper article.

    🧵 1/N

  30. Came across this again while reviewing some code in #musl iconv: the standard legacy encoding for Korean, EUC-KR/CP949, is grossly underdocumented. Unlike a most other CJK encodings, Wikipedia has basically no information on the actual encoding structure, and WHATWG chooses to specify it as an arbitrary table completely disregarding the structure.

    So, a little thread on it, so it's written down somewhere. Maybe someday someone will write a proper article.

    🧵 1/N

  31. Came across this again while reviewing some code in iconv: the standard legacy encoding for Korean, EUC-KR/CP949, is grossly underdocumented. Unlike a most other CJK encodings, Wikipedia has basically no information on the actual encoding structure, and WHATWG chooses to specify it as an arbitrary table completely disregarding the structure.

    So, a little thread on it, so it's written down somewhere. Maybe someday someone will write a proper article.

    🧵 1/N

  32. Came across this again while reviewing some code in #musl iconv: the standard legacy encoding for Korean, EUC-KR/CP949, is grossly underdocumented. Unlike a most other CJK encodings, Wikipedia has basically no information on the actual encoding structure, and WHATWG chooses to specify it as an arbitrary table completely disregarding the structure.

    So, a little thread on it, so it's written down somewhere. Maybe someday someone will write a proper article.

    🧵 1/N

  33. Came across this again while reviewing some code in #musl iconv: the standard legacy encoding for Korean, EUC-KR/CP949, is grossly underdocumented. Unlike a most other CJK encodings, Wikipedia has basically no information on the actual encoding structure, and WHATWG chooses to specify it as an arbitrary table completely disregarding the structure.

    So, a little thread on it, so it's written down somewhere. Maybe someday someone will write a proper article.

    🧵 1/N

  34. Addendum to "things #musl libc will never do":

    - Request your age, date of birth, or proof of identity or attempt to report it to applications.

  35. Addendum to "things #musl libc will never do":

    - Request your age, date of birth, or proof of identity or attempt to report it to applications.

  36. Addendum to "things #musl libc will never do":

    - Request your age, date of birth, or proof of identity or attempt to report it to applications.

  37. Addendum to "things #musl libc will never do":

    - Request your age, date of birth, or proof of identity or attempt to report it to applications.

  38. Addendum to "things #musl libc will never do":

    - Request your age, date of birth, or proof of identity or attempt to report it to applications.

  39. The public key fingerprint for #musl release signatures is:

    8364 8929 0BB6 B70F 99FF DA05 56BC DB59 3020 450F

    Republishing this here now for the first time since our move to Treehouse, to follow a past practice for redundancy of sources of trust.

  40. The public key fingerprint for #musl release signatures is:

    8364 8929 0BB6 B70F 99FF DA05 56BC DB59 3020 450F

    Republishing this here now for the first time since our move to Treehouse, to follow a past practice for redundancy of sources of trust.

  41. The public key fingerprint for #musl release signatures is:

    8364 8929 0BB6 B70F 99FF DA05 56BC DB59 3020 450F

    Republishing this here now for the first time since our move to Treehouse, to follow a past practice for redundancy of sources of trust.

  42. The public key fingerprint for #musl release signatures is:

    8364 8929 0BB6 B70F 99FF DA05 56BC DB59 3020 450F

    Republishing this here now for the first time since our move to Treehouse, to follow a past practice for redundancy of sources of trust.

  43. The public key fingerprint for #musl release signatures is:

    8364 8929 0BB6 B70F 99FF DA05 56BC DB59 3020 450F

    Republishing this here now for the first time since our move to Treehouse, to follow a past practice for redundancy of sources of trust.

  44. Idea for a #musl pin or bumper sticker:

    WE ❤️ FTMs

    😂

  45. Idea for a #musl pin or bumper sticker:

    WE ❤️ FTMs

    😂

  46. Idea for a pin or bumper sticker:

    WE ❤️ FTMs

    😂

  47. Idea for a #musl pin or bumper sticker:

    WE ❤️ FTMs

    😂

  48. Idea for a #musl pin or bumper sticker:

    WE ❤️ FTMs

    😂

  49. While watching Brodie Robertson's reaction to LTT trying Linux again, I installed Void Linux. I picked the musl base live image and after install I had to manually install xfce and sum stuffs.

    I'll be doing the stuff I've been doing in the cachyos vm here.

    #voidlinux #xfce #linux #freesoftware #opensource #runit #musl #amd #qemu #kvm #microsoft #windows10 #windows11 #microslop #linustechtips #ltt #cachyos #archlinux

  50. While watching Brodie Robertson's reaction to LTT trying Linux again, I installed Void Linux. I picked the musl base live image and after install I had to manually install xfce and sum stuffs.

    I'll be doing the stuff I've been doing in the cachyos vm here.

    #voidlinux #xfce #linux #freesoftware #opensource #runit #musl #amd #qemu #kvm #microsoft #windows10 #windows11 #microslop #linustechtips #ltt #cachyos #archlinux