shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

268
active users

#redhad

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mitexleo.one/@ml" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ml</span></a></span> I've heard of <a href="https://infosec.space/tags/RustDesk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RustDesk</span></a>, but lets just say the whole <em>"it's not <a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaaS</span></a>!"</em> when it clearly is a <a href="https://infosec.space/tags/subscription" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>subscription</span></a> <a href="https://infosec.space/tags/licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>licensing</span></a> scheme is kinda off-putting to me...<br><a href="https://rustdesk.com/pricing/?lang=en" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">rustdesk.com/pricing/?lang=en</span><span class="invisible"></span></a></p><ul><li>I mean, it is <em>"<a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a>"</em> as in <a href="https://infosec.space/tags/SUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SUSE</span></a>, <a href="https://infosec.space/tags/OracleLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OracleLinux</span></a> ( &amp; <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHad</span></a> used to be)...</li></ul><p>That doesn't mean they are bad - far from it.</p><ul><li>Tho being better than <a href="https://infosec.space/tags/TeamViewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TeamViewer</span></a> or <a href="https://infosec.space/tags/AnyDesk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AnyDesk</span></a> isn't <em>that hard</em>...</li></ul><p>I just use <a href="https://infosec.space/tags/Dayon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Dayon</span></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">#<span>TechIlliterates</span></a> when it comes to getting <a href="https://infosec.space/tags/RemoteSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RemoteSupport</span></a> up and running with them.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://goatdaddy.net/profile/vvelox" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>vvelox</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@SecurityWriter" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SecurityWriter</span></a></span> I trust noone, but unlike <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a>, <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHad</span></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">#<span>Govware</span></a> <a href="https://infosec.space/tags/Backdoors" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Backdoors</span></a> into critical compontents like the <a href="https://infosec.space/tags/CryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CryptoAPI</span></a>... </p><p><a href="https://github.com/kkarhan/windows-ca-backdoor-fix" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kkarhan/windows-ca-</span><span class="invisible">backdoor-fix</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@anderseknert" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>anderseknert</span></a></span> Everyone who uses <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a> like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> or tries to infringe upon users' <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> <a href="https://infosec.space/tags/Rights" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rights</span></a> like <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>grsecurity</span></a> &amp; <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHad</span></a> do should be banned from any professional developments and supply chains as part of the <em><a href="https://infosec.space/tags/RiskAssessment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RiskAssessment</span></a> and <a href="https://infosec.space/tags/RiskAvoidance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RiskAvoidance</span></a></em> in <a href="https://infosec.space/tags/DueDiligence" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DueDiligence</span></a>.</p><ul><li>Anything else in criminal neglect at this point...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@prem_k" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>prem_k</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@silentexception" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>silentexception</span></a></span> Well, <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> does not require that they need to make it simple for one to do so.</p><p>Both <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>grsecurity</span></a> &amp; <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHad</span></a> comply to <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> by merely providing <a href="https://infosec.space/tags/paywalled" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>paywalled</span></a> access to their repos.</p><p>They don't need to provide instructions to make reproduceable builds nor documentation nor resources to do so!</p>