Veganism Social

Kevin Karhan :verified:<a href="https://hachyderm.io/@anderseknert" class="u-url mention" rel="nofollow noopener" target="_blank">@anderseknert</a> Everyone who uses <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a> like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> or tries to infringe upon users' <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> <a href="https://infosec.space/tags/Rights" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rights</a> like <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> & <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHad</a> do should be banned from any professional developments and supply chains as part of the <a href="https://infosec.space/tags/RiskAssessment" class="mention hashtag" rel="nofollow noopener" target="_blank">#RiskAssessment</a> and <a href="https://infosec.space/tags/RiskAvoidance" class="mention hashtag" rel="nofollow noopener" target="_blank">#RiskAvoidance</a> in <a href="https://infosec.space/tags/DueDiligence" class="mention hashtag" rel="nofollow noopener" target="_blank">#DueDiligence</a>.<ul><li>Anything else in criminal neglect at this point...</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@prem_k" class="u-url mention" rel="nofollow noopener" target="_blank">@prem_k</a> <a href="https://mastodon.social/@silentexception" class="u-url mention" rel="nofollow noopener" target="_blank">@silentexception</a> Well, <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> does not require that they need to make it simple for one to do so.Both <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> & <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHad</a> comply to <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> by merely providing <a href="https://infosec.space/tags/paywalled" class="mention hashtag" rel="nofollow noopener" target="_blank">#paywalled</a> access to their repos.They don't need to provide instructions to make reproduceable builds nor documentation nor resources to do so!

Kevin Karhan :verified:<a href="https://musician.social/@soulexpress" class="u-url mention" rel="nofollow noopener" 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" 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" 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" 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" target="_blank">#Subgraph</a> evolved after <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> decided to <a href="https://infosec.space/tags/paywall" class="mention hashtag" rel="nofollow noopener" target="_blank">#paywall</a> access to the <a href="https://infosec.space/tags/sourcecodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#sourcecodes</a> of said <a href="https://infosec.space/tags/patches" class="mention hashtag" rel="nofollow noopener" target="_blank">#patches</a> and <a href="https://infosec.space/tags/tools" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">archive version</a> exists.</li></ul>

Kevin Karhan :verified:<a href="https://social.fbxl.net/users/Hyolobrika" class="u-url mention" rel="nofollow noopener" target="_blank">@Hyolobrika</a> my guess is that <a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> is hell-bent on perfection or not bothering at all.Kinda like saying <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> is shit because there is no distro paying for <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> and thus only <a href="https://infosec.space/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a> qualifies for them in terms of <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>.There are "compromises" and compromises: <a href="https://infosec.space/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#GrapheneOS</a> would <a href="https://grapheneos.social/@GrapheneOS/112882867425207102" rel="nofollow noopener" target="_blank">rather mothball than back down</a> and that's their right as a project...I just think that keeps their adoption rate artificially low so <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> can shaft them and not face much Backclash...

OS/1337Interestingly, all the people that say "<a href="https://infosec.space/tags/Copilot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Copilot</a> is violating my <a href="https://infosec.space/tags/Copyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#Copyright</a>!" and fanboy <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#BusyBox</a>'s hamfisted approach to <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> enforcement are really quiet when it comes to enforcing <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> against <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHat</a> or <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a>... <a href="https://infosec.space/tags/NotLegalAdvice" class="mention hashtag" rel="nofollow noopener" target="_blank">#NotLegalAdvice</a> but maybe it's because only those that bought the final product are entitled to the source and <a href="https://infosec.space/tags/learning" class="mention hashtag" rel="nofollow noopener" target="_blank">#learning</a> isn't <a href="https://infosec.space/tags/CopyrightInfringement" class="mention hashtag" rel="nofollow noopener" target="_blank">#CopyrightInfringement</a> because otherwise we'd all be lifelong <a href="https://infosec.space/tags/DebtPeons" class="mention hashtag" rel="nofollow noopener" target="_blank">#DebtPeons</a> to <a href="https://infosec.space/tags/Schoolbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Schoolbook</a>- & <a href="https://infosec.space/tags/Textbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Textbook</a> <a href="https://infosec.space/tags/authors" class="mention hashtag" rel="nofollow noopener" target="_blank">#authors</a> or rather their Copyright-holding <a href="https://infosec.space/tags/publishers" class="mention hashtag" rel="nofollow noopener" target="_blank">#publishers</a>! <a href="https://felixreda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/" rel="nofollow noopener" translate="no" target="_blank">https://felixreda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/</a>

Recent searches

Search options

Administered by:

Server stats:

#grsecurity