zundon

Radio Azureus$ dmesg | lolcat<a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/messagesAfterPost" class="mention hashtag" rel="nofollow noopener" target="_blank">#messagesAfterPost</a> <a href="https://mastodon.social/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> <a href="https://mastodon.social/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a> <a href="https://mastodon.social/tags/csh" class="mention hashtag" rel="nofollow noopener" target="_blank">#csh</a> <a href="https://mastodon.social/tags/ksh" class="mention hashtag" rel="nofollow noopener" target="_blank">#ksh</a> <a href="https://mastodon.social/tags/sh" class="mention hashtag" rel="nofollow noopener" target="_blank">#sh</a>

Felix Palmen :freebsd: :c64:<a href="https://mastodon.bsd.cafe/tags/xmoji" class="mention hashtag" rel="nofollow noopener" target="_blank">#xmoji</a> <a href="https://mastodon.bsd.cafe/tags/l10n" class="mention hashtag" rel="nofollow noopener" target="_blank">#l10n</a>: First pull request completed, I now have my very own translation tool and can translate all the UI texts (but not yet include the <a href="https://mastodon.bsd.cafe/tags/Unicode" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unicode</a> <a href="https://mastodon.bsd.cafe/tags/CLDR" class="mention hashtag" rel="nofollow noopener" target="_blank">#CLDR</a> translations for the emoji names, that'll be the next PR).Amazing as always, the key to getting things done is to DO these things 😂🙈. Investing a LOT of thought about whether to use <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> catalogs or GNU <a href="https://mastodon.bsd.cafe/tags/gettext" class="mention hashtag" rel="nofollow noopener" target="_blank">#gettext</a> or come up with something myself (and then, how far should I jump there) led exactly nowhere and I finally decided to just run a spike with own tooling and refine the design while coding it. Ended up with a simple (and, I think, portable) binary format for the translations, containing everything in UTF-8, but offering a flag for the translation loader to know which texts to directly convert to my "UniStr" type holding UTF-32.<a href="https://mastodon.bsd.cafe/tags/X11" class="mention hashtag" rel="nofollow noopener" target="_blank">#X11</a> <a href="https://mastodon.bsd.cafe/tags/emoji" class="mention hashtag" rel="nofollow noopener" target="_blank">#emoji</a> <a href="https://mastodon.bsd.cafe/tags/keyboard" class="mention hashtag" rel="nofollow noopener" target="_blank">#keyboard</a>

Dr. Todd A. Jacobs<a href="https://infosec.exchange/tags/TIL" class="mention hashtag" rel="nofollow noopener" target="_blank">#TIL</a> that <a href="https://mstdn.social/@GnuPG" class="u-url mention" rel="nofollow noopener" target="_blank">@GnuPG</a> appears to use the <a href="https://infosec.exchange/tags/ustar" class="mention hashtag" rel="nofollow noopener" target="_blank">#ustar</a> tar archive format, likely the version from POSIX.1-1988, for <a href="https://infosec.exchange/tags/gpgtar" class="mention hashtag" rel="nofollow noopener" target="_blank">#gpgtar</a> rather than either the <a href="https://infosec.exchange/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> or Star formats from POSIX.1-2001. Since ustar has serious limitations on filename and pathname lengths, can't store certain file types or metadata, and has a 2GB file size limit, it seems unsuitable for most modern use cases.If gpgtar is actually using star, pax, or the GNU tar POSIX mode, it's not in the <a href="https://infosec.exchange/tags/GnuPG" class="mention hashtag" rel="nofollow noopener" target="_blank">#GnuPG</a> user documentation which explicitly says it uses ustar. I have a lot of respect for the <a href="https://infosec.exchange/tags/GPG" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPG</a> devs, so I hope this is either just a documentary oversight or something that they can easily fix by linking with newer libraries. In either case, ustar is totally unsuitable for writing large archives to tape, and doesn't even offer the options GNU tar does for creating a separate index file, encrypted or not.The gnutar command line doesn't offer the option to write a separate index, and requires a separate pass to list out the index. For example if you wanted to encrypt a 20TiB archive with a separate, encrypted index to make finding files easier, you'd either have to pipe tar through gpg (which can cause shoe-shining or buffering issues on <a href="https://infosec.exchange/tags/LTFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#LTFS</a>) and then encrypt GNU/BSD tar's index, or have triple the online HDD/SDD capacity of your archived data so you can tar up your files, run another pass with GnuPG to extract the index, and then encrypt both the tarball and index separately before writing them out to tape.That seems...unreasonable. <a href="https://infosec.exchange/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenPGP</a> doesn't support the AES-256-GCM mode built into current <a href="https://infosec.exchange/tags/LTO" class="mention hashtag" rel="nofollow noopener" target="_blank">#LTO</a> drives, so gpgtar needs to keep up with the massive growth of data storage capacity rather than remaining an afterthought utility. Especially for <a href="https://infosec.exchange/tags/SOHO" class="mention hashtag" rel="nofollow noopener" target="_blank">#SOHO</a> LTO drives, the ability to write encrypted gpgtar archives and indexes directly to LTFS could be a real game-changer!

Philip GuentherI've written a diff for <a href="https://bsd.network/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#openbsd</a> to implement the new <a href="https://bsd.network/tags/posix" class="mention hashtag" rel="nofollow noopener" target="_blank">#posix</a> close-on-fork (FD_CLOFORK, O_CLOFORK, etc) flag...and as specified it seems unsafe/insecure.Specifically, it's required to be preserved across exec. So, you're supposed to be able to set the close-on-fork flag on fd 2, exec a setuid program which forks, and have stderr be closed in the child, so the next fd it opens gets stderr output!?? Wut.Does anyone have Real World experience with close-on-fork, eithera) as a application author, making intentional use of its preservation across exec, ORb) as an implementer, either who has deployed as specified (and dealt with attacks?) or who don't follow the standard on this or other points?(Please retoot if your audience may have answers)

Radio AzureusInteresting 🤔 how <a href="https://mastodon.social/tags/CVE" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE</a> are leveraged as resume items, putting <a href="https://mastodon.social/tags/programmers" class="mention hashtag" rel="nofollow noopener" target="_blank">#programmers</a> <a href="https://mastodon.social/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a> & project leads under pressure by <a href="https://mastodon.social/tags/bogus" class="mention hashtag" rel="nofollow noopener" target="_blank">#bogus</a> CVE reports or unnecessary high CVE ratings.Popular and obscure programs are affected in the <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.social/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> world e.g <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/freeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#freeBSD</a> <a href="https://mastodon.social/tags/netBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#netBSD</a> <a href="https://mastodon.social/tags/openBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#openBSD</a> <a href="https://mastodon.social/tags/Curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#Curl</a> ➰ by <a href="https://mastodon.social/tags/Daniel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Daniel</a> <a href="https://mastodon.social/tags/Stenberg" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stenberg</a> and <a href="https://mastodon.social/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> by <a href="https://mastodon.social/tags/Fedor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedor</a> <a href="https://mastodon.social/tags/Indutny" class="mention hashtag" rel="nofollow noopener" target="_blank">#Indutny</a> are popular programs hit by this <a href="https://mastodon.social/tags/phenomena" class="mention hashtag" rel="nofollow noopener" target="_blank">#phenomena</a> which can lead to unwarranted <a href="https://mastodon.social/tags/panic" class="mention hashtag" rel="nofollow noopener" target="_blank">#panic</a> in the users space <a href="https://www.bleepingcomputer.com/news/security/dev-rejects-cve-severity-makes-his-github-repo-read-only/" rel="nofollow noopener" translate="no" target="_blank">https://www.bleepingcomputer.com/news/security/dev-rejects-cve-severity-makes-his-github-repo-read-only/</a>

Hal CanaryTime for a longer #introduction.

codesectionsI've recently been trying out the <a href="https://fosstodon.org/tags/yash" class="mention hashtag" rel="nofollow noopener" target="_blank">#yash</a> shell (<a href="https://yash.osdn.jp/index.html.en" rel="nofollow noopener" target="_blank">https://yash.osdn.jp/index.html.en</a>) and think I'm going to switch to it as my full-time shell.It offers: - fish-like completion - <a href="https://fosstodon.org/tags/posix" class="mention hashtag" rel="nofollow noopener" target="_blank">#posix</a> compliance - Low memory use (compared to <a href="https://fosstodon.org/tags/fish" class="mention hashtag" rel="nofollow noopener" target="_blank">#fish</a>/#zsh) - customizable keyboard commands with built-in readline defaults(I'm leaving <a href="https://fosstodon.org/tags/ion" class="mention hashtag" rel="nofollow noopener" target="_blank">#ion</a> – nothing against it, and it still seems cool, but I'm interested in moving back towards POSIX compliance)

Recent searches

Search options

Administered by:

Server stats:

#posix