digitalcourage.social

Kevin Karhan :verified:<a href="https://mitexleo.one/@ml" class="u-url mention" rel="nofollow noopener" target="_blank">@ml</a> I've heard of <a href="https://infosec.space/tags/RustDesk" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustDesk</a>, but lets just say the whole "it's not <a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SaaS</a>!" when it clearly is a <a href="https://infosec.space/tags/subscription" class="mention hashtag" rel="nofollow noopener" target="_blank">#subscription</a> <a href="https://infosec.space/tags/licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#licensing</a> scheme is kinda off-putting to me... <a href="https://rustdesk.com/pricing/?lang=en" rel="nofollow noopener" translate="no" target="_blank">https://rustdesk.com/pricing/?lang=en</a><ul><li>I mean, it is "<a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>" as in <a href="https://infosec.space/tags/SUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SUSE</a>, <a href="https://infosec.space/tags/OracleLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#OracleLinux</a> ( & <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHad</a> used to be)...</li></ul>That doesn't mean they are bad - far from it.<ul><li>Tho being better than <a href="https://infosec.space/tags/TeamViewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#TeamViewer</a> or <a href="https://infosec.space/tags/AnyDesk" class="mention hashtag" rel="nofollow noopener" target="_blank">#AnyDesk</a> isn't that hard...</li></ul>I just use <a href="https://infosec.space/tags/Dayon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dayon</a> because it's <a href="https://retgal.github.io/Dayon/quickstart.html" rel="nofollow noopener" target="_blank">very easy to walkthrough</a> <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a> when it comes to getting <a href="https://infosec.space/tags/RemoteSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#RemoteSupport</a> up and running with them.

Kevin Karhan :verified:<a href="https://goatdaddy.net/profile/vvelox" class="u-url mention" rel="nofollow noopener" target="_blank">@vvelox</a> <a href="https://infosec.exchange/@SecurityWriter" class="u-url mention" rel="nofollow noopener" target="_blank">@SecurityWriter</a> I trust noone, but unlike <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a>, <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHad</a> didn't betray it's paying customers by literally shoving <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> <a href="https://infosec.space/tags/Backdoors" class="mention hashtag" rel="nofollow noopener" target="_blank">#Backdoors</a> into critical compontents like the <a href="https://infosec.space/tags/CryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CryptoAPI</a>... <a href="https://github.com/kkarhan/windows-ca-backdoor-fix" rel="nofollow noopener" translate="no" target="_blank">https://github.com/kkarhan/windows-ca-backdoor-fix</a>

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!

Michael DexterDoes anyone have hard facts on what % diff the <a href="https://bsd.network/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHad</a> base OS diff is from upstream?To take steps to discourage testing upstream in the name of violations by downstream suggests someone is failing to grasp how the ecosystem works.

Maxi 11x 💉Red Hat Planning A Hackfest To Further Advance HDR Support On The Linux Desktop<a href="https://www.phoronix.com/news/Red-Hat-2023-HDR-Hackfest" rel="nofollow noopener" target="_blank">https://www.phoronix.com/news/Red-Hat-2023-HDR-Hackfest</a>Forum:»I get the feeling that the Linux desktop would be more advanced if <a href="https://chaos.social/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHad</a> would not be so obsessed with Gnome only and not caring at all about other desktop environments. Interesting how everyone is invited at this event, except for the <a href="https://chaos.social/tags/KDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> developers.«

Recent searches

Search options

Administered by:

Server stats:

#redhad