Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://circumstances.run/@davidgerard" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>davidgerard</span></a></span> problem is that I can't rely on <a href="https://infosec.space/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>python</span></a> being available and being allowed to install it!</p><ul><li>Whereas <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bash</span></a> (or a subset of it as in <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a>) does exist on any <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> that isn't specifically <em>not</em> having it...</li></ul>
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.
Administered by:
Server stats:
209active users
eupolicy.social: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.1
#toybox
0 posts · 0 participants · 0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.io/@wolf480pl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>wolf480pl</span></a></span> OFC limiting the scope of a project is important.</p><ul><li>I.e. "I don't want to do a <a href="https://infosec.space/tags/GUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GUI</span></a> with like a modern desktop for <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> because that'll exceed the desired complexity and sticking to <a href="https://infosec.space/tags/TUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TUI</span></a> / <a href="https://infosec.space/tags/CLI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLI</span></a> is the best I want to do." is such a scope.</li></ul><p>OFC there are reasons why <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bash</span></a> is bash and why i.e. <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> will most likely only implement a tiny subset of bash in <a href="https://landley.net/toybox/help.html" rel="nofollow noopener" target="_blank"><code>toysh</code></a> and why <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> hasn't implemented support for <code>.bash_aliases</code> yet [if he'd ever do that considering there are more pressing <code>TODO</code>s than <em>"some hobbyist doodler's wish"</em>... </p><ul><li>Either way I don't fault either <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>developers</span></a> for that: <em>I don't pay them for their work so I don't get to tell them what they should do!</em> In fact I'm grateful for their work and that they decided to release it and license it as <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> and not <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a>...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bagder</span></a></span> Problem with that is (besides occasional bugfixes), most people including myself would see <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>curl</span></a> to be <em>functionally complete</em> and anything <em>"nice to have"</em> would be considered not worth the balooning in <a href="https://infosec.space/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>complexity</span></a> and <a href="https://infosec.space/tags/size" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>size</span></a>. </p><ul><li><p>I mean, does <a href="https://curl.se/" rel="nofollow noopener" target="_blank">curl</a> <em>need</em> to be able to do <a href="https://infosec.space/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BitTorrent</span></a> (magnet:), <a href="https://infosec.space/tags/IPFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPFS</span></a> (ipfs://) or god forbid <a href="https://infosec.space/tags/blockchain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blockchain</span></a> (i.e. <a href="https://infosec.space/tags/EVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EVM</span></a>) support? </p></li><li><p>Do you really want to integrate <span class="h-card" translate="no"><a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>torproject</span></a></span> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tor</span></a> support <em>natively into curl</em> when using <a href="https://infosec.space/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> (localhost:8118) and <a href="https://infosec.space/tags/SOCKS5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SOCKS5</span></a> (localhost:9050) <a href="https://infosec.space/tags/proxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxy</span></a> allows for the same and doesn't necessitate having to handle and ingest Tor arguments as well??</p></li></ul><p>In fact if <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> didn't have a <a href="https://infosec.space/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wget</span></a> implementation that I could use for OS/1337 I would've merely chosen <a href="https://curl.se/tiny/" rel="nofollow noopener" target="_blank"><code>tiny-curl -o</code></a> as a <a href="https://stackoverflow.com/questions/30702803/set-aliases-globally-for-all-users" rel="nofollow noopener" target="_blank">global alias</a> or if <a href="https://infosec.space/tags/tinycurl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tinycurl</span></a> wasn't an option, <a href="https://linux.die.net/man/1/curl" rel="nofollow noopener" target="_blank"><code>curl -o</code></a> instead.</p><ul><li>Maybe someone who wants to have said functionality like <code>tor</code> support built-in will go and IDK make i.e. <code>#neocurl</code> or sth. along those lines or build something like <code>#ethcurl</code> or <code>#torcurl</code>or <code>#ipfscurl</code> or whatever...</li></ul><p>That being said I am glad <code>curl</code> isn't <em>solely</em> maintained by you but has other contributors (give them a shoutout!) but I also am glad you maintain that vital software that most <em>"<a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechIlliterate</span></a> <a href="https://infosec.space/tags/Normies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Normies</span></a>"</em> most likely never heard of but propably use on a daily basis as part of all the <a href="https://infosec.space/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tech</span></a> they use to <a href="https://infosec.space/tags/consume" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>consume</span></a> media with...</p><ul><li>I consider curl to be <em>"the <a href="https://infosec.space/tags/vim" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vim</span></a> of downloaders"</em> (tho that's kinda insulting and limiting since <code>curl</code> is more than just a downloader <em>and</em> more intuitive than <code>vim</code>) with wget being <em>"the <a href="https://infosec.space/tags/vi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vi</span></a> of downloaders"</em> (tho <code>wget</code> is even simpler to use than <code>vi</code>)...</li></ul><p>Either way, curl is awesome... </p><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Enshittification</span></a> <a href="https://infosec.space/tags/Bloat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bloat</span></a> <a href="https://infosec.space/tags/Bloatware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bloatware</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@ravirockks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ravirockks</span></a></span> OFC they don't.</p><ul><li>And by <em>"don't</em> I don't mean <em>"teach <a href="https://infosec.space/tags/assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>assembly</span></a> and CPU architectures"</em> but <em>anything that goes beyond <a href="https://infosec.space/tags/LinusTechTips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinusTechTips</span></a>'s <a href="https://infosec.space/tags/Tutorials" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tutorials</span></a></em>...</li></ul><p>At best they show people how to change fan curves in the <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a> or hiw to run <a href="https://infosec.space/tags/memtest86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memtest86</span></a>+, but mostly they just <em>"teach" people how to consume <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> and at best <a href="https://infosec.space/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a></em> and that's it.</p><ul><li>I mean I don't expect any training center to teach people how to build <a href="https://infosec.space/tags/mkroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mkroot</span></a> (<a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> + <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a>) or <a href="https://infosec.space/tags/LinuxFromScratch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxFromScratch</span></a> but at least showing people how to use <span class="h-card" translate="no"><a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ubuntu</span></a></span> / <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UbuntuLTS</span></a> & <span class="h-card" translate="no"><a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tails_live</span></a></span> / <span class="h-card" translate="no"><a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tails</span></a></span> / <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tails</span></a> should be in the cards if <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RHEL</span></a> & <a href="https://infosec.space/tags/SLES" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SLES</span></a> / <a href="https://infosec.space/tags/SLED" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SLED</span></a> isn't.</li></ul><p>Same with <span class="h-card" translate="no"><a href="https://fosstodon.org/@libreoffice" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>libreoffice</span></a></span> / <a href="https://infosec.space/tags/LibreOffice" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LibreOffice</span></a> & <span class="h-card" translate="no"><a href="https://mastodon.online/@thunderbird" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thunderbird</span></a></span> / <a href="https://infosec.space/tags/Thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Thunderbird</span></a>.</p><ul><li>At least the most pointless certification - <a href="https://infosec.space/tags/ECDL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ECDL</span></a> - isn't hard-locked to <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows11</span></a> & <a href="https://infosec.space/tags/MicrosoftOffice" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MicrosoftOffice</span></a> <em>per-se</em>!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://expressional.social/@notsoloud" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>notsoloud</span></a></span> same with all other <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> distros.</p><ul><li>Guess why <a href="https://infosec.space/tags/NORAD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NORAD</span></a> used <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a> and why I started my own minimalist, <a href="https://infosec.space/tags/GNUfree" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNUfree</span></a> <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> + <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></a> / <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> distro: <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> ...</li></ul><p>Now granted, <a href="https://infosec.space/tags/NvChad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NvChad</span></a> is basically what happens when <a href="https://infosec.space/tags/neovim" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>neovim</span></a> fans want to make a better alternative to <a href="https://infosec.space/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>emacs</span></a>.</p><ul><li>Personally, I only put it ob a <a href="https://infosec.space/tags/wishlist" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wishlist</span></a> <a href="https://github.com/OS-1337/pkgs/blob/main/docs/WISHLIST.tsv#L11" rel="nofollow noopener" target="_blank">of sorts</a> because I want to make a 80x25-optimized <a href="https://infosec.space/tags/TUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TUI</span></a> <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Desktop</span></a> easier to accomplish.</li></ul><p>For most people, using <a href="https://infosec.space/tags/fish" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fish</span></a> as in <a href="https://fishshell.com" rel="nofollow noopener" target="_blank">fish shell</a> with <a href="https://infosec.space/tags/tmux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tmux</span></a> and some extras could yield the same...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GrapheneOS</span></a></span> Well, you've to ask <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a> and <a href="https://infosec.space/tags/Fiarphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fiarphone</span></a> that and consider invoking <a href="https://infosec.space/tags/Regulators" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Regulators</span></a> like <span class="h-card" translate="no"><a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>EUCommission</span></a></span>, @kartellamt@social.bund.de and others in that matter.</p><p>Which again proves my point:</p><ol><li><p><a href="https://infosec.space/tags/AllGAFAMsAreEvil" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AllGAFAMsAreEvil</span></a> and <em>NOONE</em> shoud've ever trusted them with anything!</p></li><li><p>The <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> ecosystem is fucked up and there is a need for <a href="https://infosec.space/tags/vendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vendors</span></a> to refuse to bow before <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a> and actually do <a href="https://infosec.space/tags/secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>secure</span></a> & <a href="https://infosec.space/tags/repairable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>repairable</span></a> devices.</p></li></ol> <p>Again: You seem angry at the wromg person if that means you're angry at me.</p><p>The question to me is how is <a href="https://infosec.space/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GrapheneOS</span></a> gonna go about this? </p><ul><li>Cuz we both know Google can afford to go <em>"maximum asshole"</em> on you [the Grpahnene OS Project] and even in the worst case their legal department won't even notice this whole shitshow even if miraculously by the wounders of everyone from <span class="h-card" translate="no"><a href="https://mastodon.social/@eff" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>eff</span></a></span> to <span class="h-card" translate="no"><a href="https://hostux.social/@fsf" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fsf</span></a></span> to <span class="h-card" translate="no"><a href="https://mastodon.social/@noybeu" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>noybeu</span></a></span> and <span class="h-card" translate="no"><a href="https://social.bau-ha.us/@CCC" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>CCC</span></a></span> forcing Google to literally support and endore GrapheneOS, because by the time any binding court ruling would be enforced, Google would've choked the project out of the market.</li></ul> <p>So my question is <em>when</em> will you get forward and work with other <a href="https://infosec.space/tags/vendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vendors</span></a> instead of tying your project to Google-specific and thus sorta-proprietary implementations?</p><p><code>[...] Pixel targets have a lot of device-specific hardening in the AOSP base along with some in GrapheneOS which needs to be ported over too. For example, various security features in the kernel including type-based Control Flow Integrity (CFI) and the shadow call stack are currently specific to the kernels for these devices. [...]</code></p><ul><li><a href="https://grapheneos.org/build#building-grapheneos" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">grapheneos.org/build#building-</span><span class="invisible">grapheneos</span></a></li></ul><p>To me that sounds like some very serious <a href="https://infosec.space/tags/VendorLockIn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VendorLockIn</span></a> you're stuck in, and now it bites you in your rear...</p><p>I hate to say it, but <a href="https://infosec.space/tags/ToldYaSo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ToldYaSo</span></a> sadly happened!</p><p>I guess you gotta have to <a href="http://landley.net/toybox/" rel="nofollow noopener" target="_blank">bootstrap it from scratch</a> starting with <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> + musl / <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> sooner or later...</p> <p>Not to seem like an asshole, but I do sincerely wish GrpaheneOS and it's team only the best of luck and that the issue gets fixed sooner than later, because this <a href="https://infosec.space/tags/Vendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vendor</span></a> <a href="https://infosec.space/tags/LockIn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LockIn</span></a> is a major issue [and yes I do blame the Device Vendors that shit out unmaintained garbage] so unless you can afford the legal cost of actuall enforcing <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EU</span></a> laws re: <a href="https://infosec.space/tags/SecurityUpdates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SecurityUpdates</span></a> and force Vendors like <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fairphone</span></a> to actually follow their claims re: <a href="https://infosec.space/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> and <a href="https://infosec.space/tags/Updates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Updates</span></a>, this won't move anywhere.</p><ul><li>Yes I know you don't have that money and I don't expect this to be the case! </li></ul><p>I do however also don't expect you to find a magical solution. My point is that there needs to be a change of strategy, and relying on Hardware you neither <em>own</em> nor <em>control</em> in the sense of Stakeholding isn't going to provide you with the necessary stability.</p><ul><li>Because Google is a [pulicly traded] <a href="https://infosec.space/tags/Corporation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Corporation</span></a> and Corporations are explicity nobody's friend!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.afront.org/@warthog9" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>warthog9</span></a></span> <span class="h-card" translate="no"><a href="https://social.afront.org/@kwf" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kwf</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> </p><p>I want to use <a href="https://infosec.space/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BitTorrent</span></a> & <a href="https://infosec.space/tags/IPFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPFS</span></a> because it incentivizes users to share...</p><p>Granted I'd not use that for <a href="https://infosec.space/tags/packages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>packages</span></a> because I want to use the regular-ass <a href="https://infosec.space/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wget</span></a> implementation as included in <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> for that because it's already there...<br><a href="https://github.com/OS-1337/spm" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/OS-1337/spm</span><span class="invisible"></span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@Viss" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Viss</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@lcamtuf" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lcamtuf</span></a></span> no, you can blame <a href="https://infosec.space/tags/xz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xz</span></a> and <a href="https://infosec.space/tags/lzma" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lzma</span></a> and <a href="https://infosec.space/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> for that.</p><p><a href="https://infosec.space/tags/Dropbear" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Dropbear</span></a> and any <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></a> + <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a>-based <a href="https://infosec.space/tags/distros" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>distros</span></a> seem unaffected.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@starchy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>starchy</span></a></span> That's why I'm asking.</p><p>I am the maintainer of <span class="h-card" translate="no"><a href="https://infosec.exchange/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> and I do want to enshure it's not affected by it...</p><p>After all, it uses <span class="h-card" translate="no"><a href="https://mstdn.social/@linux" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>linux</span></a></span>, <span class="h-card" translate="no"><a href="https://fosstodon.org/@musl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>musl</span></a></span>, <a href="https://infosec.space/tags/Toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Toybox</span></a> and <a href="https://infosec.space/tags/dropbear" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dropbear</span></a> and for building it does utilize the <a href="https://infosec.space/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GCC</span></a> since it seems.as if <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> doesn't like being built by <a href="https://infosec.space/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLVM</span></a>...</p>
OS/1337<p>Tangents aside, people are free to create forks and even branches that include <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SystemD</span></a> or use <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a>: </p><p>That is the <a href="https://infosec.space/tags/Freedom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Freedom</span></a> of <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> and in fact for anything outside the 1440kB target we'd accept <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SystemD</span></a> since it works and solves a lot of issues... <br><a href="https://www.youtube.com/watch?v=o_AIw9bGogo" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=o_AIw9bGog</span><span class="invisible">o</span></a></p><p>Granted OS/1337 isn't a <a href="https://infosec.space/tags/demo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>demo</span></a> first but rather tries to take the concept of <a href="https://infosec.space/tags/tomsrtbt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tomsrtbt</span></a> and <span class="h-card" translate="no"><a href="https://fosstodon.org/@w84death" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w84death</span></a></span> 's <a href="https://infosec.space/tags/Floppinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Floppinux</span></a> and tries to make it something that is useable and can be extended to arbitrary complexity if one desires to...</p><p>It's about making a tiny <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> distro that is <a href="https://infosec.space/tags/reproduceable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reproduceable</span></a> and <a href="https://infosec.space/tags/auditable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>auditable</span></a>...</p><p>It won't replace <span class="h-card" translate="no"><a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ubuntu</span></a></span> or any other big distro, likely it won't even replace <a href="https://infosec.space/tags/mkroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mkroot</span></a> from <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> but it should be a clean and level foundation for small <a href="https://infosec.space/tags/IoT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IoT</span></a> and <a href="https://infosec.space/tags/EmbeddedSystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EmbeddedSystems</span></a> projects and products...</p><p>Something that is easy to build and customize and port to other platforms...</p><p>And we're open for contributions:<br><a href="https://github.com/OS-1337/OS1337/blob/main/docu/ideas/architectures.tsv" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/OS-1337/OS1337/blob</span><span class="invisible">/main/docu/ideas/architectures.tsv</span></a></p>
OS/1337<p>Someone asked "Why don't you use BusyBox?</p><p>Let me answer this simply...</p><p>1. <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a>'s <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Licensing</span></a> page kinda makes them look <a href="https://infosec.space/tags/toxic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toxic</span></a>...<br><a href="https://busybox.net/license.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">busybox.net/license.html</span><span class="invisible"></span></a></p><p>And <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> went into great detail on why the whole "enforcement" backfired very hard:<br><a href="https://www.youtube.com/watch?v=MkJkyMuBm3g&t=301s" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=MkJkyMuBm3</span><span class="invisible">g&t=301s</span></a></p><p>2. <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> on the other hand is very much a drop-in replacement and it's <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>0BSD</span></a> licensed, so much less headaches...<br><a href="http://landley.net/toybox/license.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">http://</span><span class="ellipsis">landley.net/toybox/license.htm</span><span class="invisible">l</span></a></p><p>So it was chosen for OS/1337:<br><a href="https://github.com/OS-1337/OS1337/blob/main/LICENSE.md" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/OS-1337/OS1337/blob</span><span class="invisible">/main/LICENSE.md</span></a></p><p>3. We use unmodified source code as of today and thus can just link to the original sources and attribute them properly:<br><a href="https://github.com/OS-1337/OS1337/blob/main/docu/LICENSES.md" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/OS-1337/OS1337/blob</span><span class="invisible">/main/docu/LICENSES.md</span></a></p><p><a href="https://infosec.space/tags/NotLegalAdvice" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NotLegalAdvice</span></a> but AFAICS this is sufficient for compliance.</p><p>I</p>
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload