Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://toot.cat/@riley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>riley</span></a></span> Case in point, <a href="https://infosec.space/tags/IrDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IrDA</span></a> on optical bandwiths would work excellent for <a href="https://infosec.space/tags/DataExchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DataExchange</span></a> on <a href="https://infosec.space/tags/airgapped" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>airgapped</span></a> <a href="https://en.wikipedia.org/wiki/Air_gap_(networking)#Examples" rel="nofollow noopener" target="_blank">systems</a> with minimal risk of violating <a href="https://infosec.space/tags/TEMPEST" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TEMPEST</span></a> <a href="https://en.wikipedia.org/wiki/Tempest_(codename)#Shielding_standards" rel="nofollow noopener" target="_blank">or similar standards</a>, thus making <a href="https://en.wikipedia.org/wiki/Red/black_concept" rel="nofollow noopener" target="_blank">RED/BLACK</a> seperation in various projects on mine simpler.</p><ul><li>Not to mention it's trivial to spoof or merely jam <a href="https://infosec.space/tags/wireless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wireless</span></a> <a href="https://infosec.space/tags/RF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RF</span></a> like <a href="https://infosec.space/tags/NFC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NFC</span></a>]<a href="https://en.wikipedia.org/wiki/Near-field_communication" rel="nofollow noopener" target="_blank">*</a> and thus denying the ability to use these, whereas it's harder to block a line-of-sight without being identified as root cause of it.</li></ul>