Encryption – Occurative https://blog.occurative.com Robert Hollingshead's Blog Mon, 11 Mar 2024 18:08:18 +0000 en-US hourly 1 https://wordpress.org/?v=6.7 https://i0.wp.com/blog.occurative.com/wp-content/uploads/2023/11/cropped-dd9899d2-8d88-4866-b6ea-503bdd099be8.png?fit=32%2C32&ssl=1 Encryption – Occurative https://blog.occurative.com 32 32 226310737 Computers, Ham Radio, and Trusted Computing https://blog.occurative.com/2024/03/11/computers-ham-radio-and-trusted-computing/ Mon, 11 Mar 2024 18:08:18 +0000 https://blog.occurative.com/?p=177 Continue reading Computers, Ham Radio, and Trusted Computing ]]> I recently acquired my Technicians license and discovered an opportunity I had not known about, but now that I know about it I look forward to exploiting it. .

The FCC stipulates as part of the rules around being a licensed amateur, I am unable to encrypt or obscure the the content of any message. I may encode (not encrypt) as long as the ability to decode is part of the public record. The only exception to this is remote control of things like space stations (AMSAT) where the control point needs to be authorized.

This got me to thinking about how such regulations would apply to trusted computing. And now I want to take that to the next level. As an academic exercise, just how far can I take an “air gapped” (as in unplugged from the internet) computer network and still ensure that there is trust. What does trust look like in this scenario? What needs to be trusted?

I intend to find out!

TTFN!

]]>
standard 177