med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

370
active users

#securecomputing

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@samirx" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>samirx</span></a></span> The idea of something like <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>OS1337</span></a></span> on a <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ROM</span></a> chip is that it it basically hardwired ROM so one can only read it and it could do some signature and checksum checking.</p><p>Granted this is a sort-of <em>primitive <a href="https://infosec.space/tags/SecureComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureComputing</span></a></em> aimed at making <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSH</span></a>-<a href="https://infosec.space/tags/Terminals" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terminals</span></a> tick...</p><p>Something <span class="h-card" translate="no"><a href="https://mastodon.social/@stman" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stman</span></a></span> and <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>landley</span></a></span> did inspire me in part... </p><ul><li>Just right now I've to tend <em>more crucial things</em>...</li></ul>
Kevin Karhan :verified:<p>-- :please_boost: 🔁 :boost_ok: :boost: :boosted:</p><p>Speaking of <a href="https://infosec.space/tags/ROMs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ROMs</span></a> for <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ix86</span></a> / <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amd64</span></a>: Does anyone know a good way to implement something like <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> in <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ROM</span></a> like the <a href="https://infosec.space/tags/Tandy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tandy</span></a> <a href="https://infosec.space/tags/1000RL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>1000RL</span></a> &amp; <a href="https://infosec.space/tags/1000RLX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>1000RLX</span></a> <a href="https://www.youtube.com/watch?v=JIEPqD4luG8&amp;t=166s" rel="nofollow noopener noreferrer" target="_blank">did</a> with <a href="https://infosec.space/tags/MSDOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MSDOS</span></a> &amp; <a href="https://infosec.space/tags/DeskMate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DeskMate</span></a> (as <span class="h-card" translate="no"><a href="https://mastodon.social/@vwestlife" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>vwestlife</span></a></span> showed)...</p><ul><li>Or is this something that requires either going down the <a href="https://infosec.space/tags/PCIe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PCIe</span></a> -&gt; <a href="https://infosec.space/tags/PCI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PCI</span></a> -&gt; <a href="https://infosec.space/tags/ISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISA</span></a> rabbit hole?</li></ul><p>I mean, it would be a way cleaner setup to boot OS/1337 to than booting a <a href="https://infosec.space/tags/CDROM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CDROM</span></a>? </p><ul><li>If noone has an Idea how to make this happen, is there any good way or existing solution to basically make a hardware write-protectable / <a href="https://infosec.space/tags/readonly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>readonly</span></a> <a href="https://infosec.space/tags/USB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>USB</span></a> flashdrive to boot from? </li></ul><p>Ideally something that can take <a href="https://infosec.space/tags/BIOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BIOS</span></a>-style ROM Chips that one can put on a board without write-enable connected so they're read-only! </p><ul><li>And yes, <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>landley</span></a></span> may see similarities to his [deprecated] <a href="https://landley.net/code/aboriginal/" rel="nofollow noopener noreferrer" target="_blank">Aboriginal Linux</a> nee <a href="https://infosec.space/tags/FirmwareLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FirmwareLinux</span></a> ...</li></ul><p>Still having like a <a href="https://infosec.space/tags/minimalist" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>minimalist</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> distro in Boot-ROM would be nifty, espechally when it comes to making a <a href="https://infosec.space/tags/SecureComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureComputing</span></a> <em>"<a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSH</span></a> <a href="https://infosec.space/tags/Terminal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Terminal</span></a>"</em>...</p><ul><li>Maybe <span class="h-card" translate="no"><a href="https://bitbang.social/@ActionRetro" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ActionRetro</span></a></span>, <span class="h-card" translate="no"><a href="https://studio8502.ca/@mos_8502" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mos_8502</span></a></span> and others can point this question to people who are firm in boot ROMs and potentially even have something at hand.</li></ul><p>(I don't expect something like a PCI(e Mini)Card but I'd not be against it!)</p><p><a href="https://infosec.space/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RetroComputing</span></a> <a href="https://infosec.space/tags/Hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hardware</span></a> <a href="https://infosec.space/tags/Question" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Question</span></a> <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ix86</span></a> <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amd64</span></a></p>
Purism<p>Hardware kill switches. Open source OS. No data collection. That's the Purism difference.<br><a href="https://puri.sm/posts/smartphones-leaking-data/" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">puri.sm/posts/smartphones-leak</span><span class="invisible">ing-data/</span></a><br><a href="https://social.librem.one/tags/PrivacyMatters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PrivacyMatters</span></a> <a href="https://social.librem.one/tags/DataSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DataSecurity</span></a> <a href="https://social.librem.one/tags/MadeInUSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MadeInUSA</span></a> <a href="https://social.librem.one/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> <a href="https://social.librem.one/tags/LibertyPhone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LibertyPhone</span></a> <a href="https://social.librem.one/tags/Purism" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Purism</span></a> <a href="https://social.librem.one/tags/DigitalPrivacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DigitalPrivacy</span></a> <a href="https://social.librem.one/tags/SecureComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureComputing</span></a> <a href="https://social.librem.one/tags/NoDataLeaks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NoDataLeaks</span></a> <a href="https://social.librem.one/tags/TechEthics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechEthics</span></a> <a href="https://social.librem.one/tags/HardwareKillSwitch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HardwareKillSwitch</span></a> <a href="https://social.librem.one/tags/PureOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PureOS</span></a> <a href="https://social.librem.one/tags/PrivacyByDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PrivacyByDesign</span></a> <a href="https://social.librem.one/tags/SecureSmartphone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureSmartphone</span></a> <a href="https://social.librem.one/tags/TechFreedom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechFreedom</span></a></p>
Cory Doctorow<p>Starting with <a href="https://mamot.fr/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microsoft</span></a>'s <a href="https://mamot.fr/tags/palladium" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>palladium</span></a> they theorized a new "<a href="https://mamot.fr/tags/SecureComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureComputing</span></a>" model for allowing companies to reach into your computer long after you had paid for it and brought it home, in order to discipline you for using it in ways that undermined its shareholders' interest.</p><p>Secure Computing began with the idea of shipping every computer with *two* CPUs. The first one was the normal CPU, the one you interacted with when you booted it up, loaded your OS, and ran programs. </p><p>25/</p>