Shakedown Social

0 posts0 participants0 posts today

Kevin Karhan :verified:<a href="https://possum.city/@tauon" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tauon</a> <a href="https://limepeeps.perchinup.top/@radmin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@radmin</a> granted <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SystemD</a> is a suite of utilities and like the <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a> patches & tools they work best together.<ul><li>OFC the criticism is valid and I don't deny the problems that occur not just to you...</li></ul>All I'm saying is that what came before was objectively worse!<ul><li>Personally <a href="https://possum.city/notes/a7vl18qge7x200ez" rel="nofollow noopener noreferrer" target="_blank">I had the opposite experience</a> cuz once you want to find a mistake, <a href="https://infosec.space/tags/journalctl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#journalctl</a> actually prints useful error messages with <code>journalctl -xe $ServiceName</code> …</li></ul>

Kevin Karhan :verified:<a href="https://fosstodon.org/@carlwgeorge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@carlwgeorge</a> <a href="https://mastodon.bsd.cafe/@vermaden" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vermaden</a> <a href="https://fosstodon.org/@samurro" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@samurro</a> <a href="https://mastodon.bsd.cafe/@tara" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tara</a> Well, that confirms you went <a href="https://infosec.space/tags/ReplyGuy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReplyGuy</a> on me in the most disingenious way possible, wasting everyones' time and patience in the process.<ul><li>Gues what: Good luck with that sales.pitch, cuz I'd rather give <a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ubuntu</a> or <a href="https://fosstodon.org/@opensuse" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@opensuse</a> my money cuz that nonchalant attitude is insulting.</li></ul>If you (or <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedHat</a> / <a href="https://infosec.space/tags/IBM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IBM</a>) don't want to support <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> or anyone using anything they made for <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RHEL</a> without paying, then shure you can do that but then don't expect people to like you.<ul><li><a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a> already did that and I'm shure it resulted in 0 extra customers.</li></ul><a href="https://infosec.space/tags/CentOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CentOS</a> was in fact a "gateway distro" and had Red Hat not axed it I would've convinced my (fmr.) boss to consider paying for an RHCSA, but alas I've invested time and effort migrating from CentOS to <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UbuntuLTS</a> and even negotiated commercial support from <a href="https://infosec.space/tags/Canonical" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Canonical</a> instead, because they were more friendly and welcoming.<ul><li>Personally, I think that Red Hat should just be honest and just stop any <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> contributions, instead try to upsell their customers to <a href="https://infosec.space/tags/zOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zOS</a> on z/Architecture <a href="https://infosec.space/tags/Mainframe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mainframe</a>|s instead cuz that was such a great business...</li></ul>Even "Source Available" like <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tarsnap</a> is better - espechally in <a href="https://infosec.space/tags/finance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#finance</a> - because having actual <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceCode</a> available is a matter of <a href="https://infosec.space/tags/trust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#trust</a>.<ul><li>And <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> is the reason people choose <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> over <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Solaris</a> and other <a href="https://infosec.space/tags/Unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Unix</a>-esque OSes.</li></ul>But I'm not getting paid to prevent Red Hat from continuing to shoot itself in the foot...<ul><li>In fact, I'd love to short it into the ground!</li></ul><a href="https://infosec.space/@kkarhan/113065846313541796" translate="no" rel="nofollow noopener noreferrer" target="_blank">https://infosec.space/@kkarhan/113065846313541796</a><a href="https://infosec.space/tags/thxbye" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#thxbye</a> <a href="https://infosec.space/tags/next" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#next</a> <a href="https://infosec.space/tags/EOD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EOD</a>

Kevin Karhan :verified:<a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@marcan</a> <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuchsiii</a> kinda gives me <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsecurity</a> & <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RHEL</a> - flashbacks: cuz <a href="https://infosec.space/tags/paywalling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#paywalling</a> <a href="https://infosec.space/tags/SourcecodeAccess" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourcecodeAccess</a> to paying <a href="https://infosec.space/tags/subscribers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#subscribers</a> and penalizing them aka. firing them as clients for exercising their right to share/modify/redistribute the <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceCode</a> is inherently an asshole move but apparently legal.<ul><li>Since <a href="https://infosec.space/tags/BrucePerens" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BrucePerens</a> failed to sue <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a> into not doing that and <a href="https://infosec.space/tags/IBM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IBM</a> took notice when they bought <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedHat</a>.</li></ul> Not shure if a <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> that governs things beyond the useage rights of a <a href="https://infosec.space/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> is even legally enforceable in Germany amd many other juristictions... <ul><li>I'd certainly rather blow €€€€ on a lawyer instead of playing "<a href="https://infosec.space/tags/FuckAroundAndFindOit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FuckAroundAndFindOit</a>" and facing insolvency-inducing "cease and decist letters" from competitiors by having flatout-illegal terms...</li></ul><a href="https://infosec.space/tags/WhatYouAllowIsWhatWillContinue" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatYouAllowIsWhatWillContinue</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> but then again, <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a> <a href="https://lkml.iu.edu/hypermail/linux/kernel/1706.2/06228.html" rel="nofollow noopener noreferrer" target="_blank">really didn't cooperate</a> and I know why most people didn't bother to <a href="https://www.linux-magazin.de/news/kernel-security-linus-disst-grsecurity/" rel="nofollow noopener noreferrer" target="_blank">even consider them</a>.

Kevin Karhan :verified:Sadly the <a href="https://infosec.space/tags/paywalling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#paywalling</a> of <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a> / <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsecurity</a> also killed more <a href="https://infosec.space/tags/downstream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#downstream</a> projects like <a href="https://web.archive.org/web/20191230091137/https://en.wikipedia.org/wiki/Tor-ramdisk" rel="nofollow noopener noreferrer" target="_blank">tor-ramdisk</a> which was a minimalist <a href="https://infosec.space/tags/busybox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#busybox</a> / <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://infosec.space/tags/distro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#distro</a> <a href="https://blogs.gentoo.org/blueness/2014/05/23/tor-ramdisk-a-tiny-embedded-image-to-host-a-tor-relay-or-exit/" rel="nofollow noopener noreferrer" target="_blank">designed</a> to host <a href="https://infosec.space/tags/OnionServices" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OnionServices</a>. It was <a href="https://tor-talk.torproject.narkive.com/jgOoi0bN/tor-ramdisk-20160810-released" rel="nofollow noopener noreferrer" target="_blank">pretty nifty</a> and the <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceCode</a> is <a href="https://gitlab.torproject.org/legacy/gitolite/tor-ramdisk/" rel="nofollow noopener noreferrer" target="_blank">still</a> <a href="https://web.archive.org/web/20200329155520/https://gitweb.torproject.org/tor-ramdisk.git" rel="nofollow noopener noreferrer" target="_blank">online</a> and hosted by <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> on their <a href="https://infosec.space/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a>, abeit seemingly abandoned since 2018...

Kevin Karhan :verified:<a href="https://musician.social/@soulexpress" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@soulexpress</a> nodds in agreement <ul><li>EVERY SINGLE ONE OF THEM!</li></ul>Like there's a reason I only got a copy of <a href="https://infosec.space/tags/SubgraphOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SubgraphOS</a> as non-public alpha under the precondition to not redistribute and was allowed to <a href="https://www.youtube.com/watch?v=AAdzyCQdxvE" rel="nofollow noopener noreferrer" target="_blank">preview it</a> because that thing was unstable and had a lot of known issues the devs were working on to get fixed.<ul><li>It's not as if they weren't aware of those, but they also didn't want "<a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechIlliterates</a>" using it with a false belief in it being ready to use and trust in.</li></ul>Not shure how <a href="https://infosec.space/tags/Subgraph" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Subgraph</a> evolved after <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsecurity</a> decided to <a href="https://infosec.space/tags/paywall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#paywall</a> access to the <a href="https://infosec.space/tags/sourcecodes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sourcecodes</a> of said <a href="https://infosec.space/tags/patches" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#patches</a> and <a href="https://infosec.space/tags/tools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tools</a> cuz those were used in said distro as a means to harden it.<ul><li>But then again the <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a> devs seem to be so toxic, their entire Wikipedia Article got nuked and only an old <a href="https://web.archive.org/web/20200201055409/https://en.wikipedia.org/wiki/grsecurity" rel="nofollow noopener noreferrer" target="_blank">archive version</a> exists.</li></ul>

Kevin Karhan :verified:<a href="https://equestria.social/@SweetAIBelle" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@SweetAIBelle</a> <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> shure.I'm convinced that a fully-fledged image of that would be similar to <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toybox</a>'s <a href="https://infosec.space/tags/mkroot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mkroot</a>, which is <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> 's reference implementation for a toxbox + <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a> / <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> system.<ul><li>Last time I checked it came out just below 4 MB, but that was the premade image using only the stuff <a href="https://youtu.be/MkJkyMuBm3g" rel="nofollow noopener noreferrer" target="_blank">toybox included</a> [and linux & being statically compiled against musl] like <a href="https://infosec.space/tags/gzip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gzip</a> instead of <a href="https://infosec.space/tags/xz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xz</a> for compression, so there already is room to shave a few hundred kB without reducing functionality out of the get-go as I've seen with my build tests of <a href="https://infosec.space/tags/kernel666" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kernel666</a>...</li></ul>Either way, we're close to <a href="https://youtu.be/cz6iGrhnMKs" rel="nofollow noopener noreferrer" target="_blank">his reference matterial</a> AFAICT and I do think that OS/1337 can become a good and solid foundation for <a href="https://infosec.space/tags/minimalist" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#minimalist</a> & <a href="https://infosec.space/tags/embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embedded</a> systems. For comparison:<ul><li><a href="https://infosec.space/tags/YoctoLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#YoctoLinux</a> is <a href="https://www.yoctoproject.org/" rel="nofollow noopener noreferrer" target="_blank">quite</a> <a href="https://infosec.space/tags/THICC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#THICC</a> in comparison (using LSB & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUtils</a> for the most part!) and stuff like <a href="https://infosec.space/tags/OpenADK" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenADK</a> seems to be overly complex...<ul><li>tho <a href="https://infosec.space/tags/Viprinet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Viprinet</a> <a href="https://www.viprinet.com/en/support/downloads#viprinux" rel="nofollow noopener noreferrer" target="_blank">hasn't updated their stuff in like 8 years</a> and I sincerely hope that's just them loginwalling access to <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceCode</a> like <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsecurity</a> to paying customers only and not them such old Kernels.</li></ul></li></ul> Speaking of <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a>, I wounder if Bruce Perens actually sued them for allegedly violating <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv2</a> when in fact said license allows <a href="https://infosec.space/tags/paywalling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#paywalling</a> aka. restricting access to buyers of the product it contains.<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OS1337</a>

OS/1337Similarly, a lot of decisions are mostly done out of necessity [i.e. <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SystemD</a> doesn't fit into 1440kB] or due to licensing conflicts [i.e. <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsec</a> /#grsecurity is <a href="https://infosec.space/tags/paywalling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#paywalling</a> access to it's sources so we won't even consider it as <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a>... ] <a href="https://grsecurity.net" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://grsecurity.net</a>Also apparently grsec managed to get their [ <a href="https://infosec.space/tags/Wikipedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wikipedia</a> article wiped ]( <a href="https://en.wikipedia.org/wiki/Grsecurity" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/Grsecurity</a> ) so [WaybackMachine to the rescue]( <a href="https://web.archive.org/web/20190429055854/https://en.wikipedia.org/wiki/Grsecurity" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://web.archive.org/web/20190429055854/https://en.wikipedia.org/wiki/Grsecurity</a> )...So yeah... I hope that answers the question...

Recent searches

Search options

Administered by:

Server stats:

#grsec