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:

264
active users

#securecomputing

0 posts0 participants0 posts today
Kevin Karhan :verified:<p>Now people may ask things like: <em>"Why?"</em> and the answer is: For a primitive approach to <a href="https://infosec.space/tags/SecureComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SecureComputing</span></a>.</p><ul><li>Because loading the <a href="https://infosec.space/tags/OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS</span></a> into <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a> allows not just for a non-persistent setup like an <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a>-<a href="https://infosec.space/tags/Terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Terminal</span></a> (think <a href="https://infosec.space/tags/VT320" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VT320</span></a> but better!) but being hard-wired as <a href="https://infosec.space/tags/ReadOnly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ReadOnly</span></a> means it's <em>tamper proof</em> by design when combined with an intrusion-detection &amp; tamper-proof seals: Physical Access will be detectable and Remote Access cannot cause permanent damages.</li></ul><p>And that may also be useful with other <a href="https://infosec.space/tags/ThinClient" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinClient</span></a>-like <em>"aplianced"</em> devices.</p><ul><li>Basically for anything where <a href="https://infosec.space/tags/NetworkBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetworkBoot</span></a> ain't an option for <em>whatever</em> reasons!</li></ul><p><a href="https://www.youtube.com/watch?v=RuZUPpmXfT0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">youtube.com/watch?v=RuZUPpmXfT0</span><span class="invisible"></span></a> via <span class="h-card" translate="no"><a href="https://bbs.kawa-kun.com/users/lazygamereviews" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lazygamereviews</span></a></span></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@samirx" class="u-url mention" rel="nofollow noopener" 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" target="_blank">@<span>OS1337</span></a></span> on a <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>SecureComputing</span></a></em> aimed at making <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a>-<a href="https://infosec.space/tags/Terminals" class="mention hashtag" rel="nofollow noopener" 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" 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" 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" target="_blank">#<span>ROMs</span></a> for <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ix86</span></a> / <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>Linux</span></a> in <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROM</span></a> like the <a href="https://infosec.space/tags/Tandy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tandy</span></a> <a href="https://infosec.space/tags/1000RL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>1000RL</span></a> &amp; <a href="https://infosec.space/tags/1000RLX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>1000RLX</span></a> <a href="https://www.youtube.com/watch?v=JIEPqD4luG8&amp;t=166s" rel="nofollow noopener" target="_blank">did</a> with <a href="https://infosec.space/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MSDOS</span></a> &amp; <a href="https://infosec.space/tags/DeskMate" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">#<span>PCIe</span></a> -&gt; <a href="https://infosec.space/tags/PCI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PCI</span></a> -&gt; <a href="https://infosec.space/tags/ISA" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">#<span>readonly</span></a> <a href="https://infosec.space/tags/USB" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">@<span>landley</span></a></span> may see similarities to his [deprecated] <a href="https://landley.net/code/aboriginal/" rel="nofollow noopener" target="_blank">Aboriginal Linux</a> nee <a href="https://infosec.space/tags/FirmwareLinux" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>minimalist</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>SecureComputing</span></a> <em>"<a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a> <a href="https://infosec.space/tags/Terminal" class="mention hashtag" rel="nofollow noopener" 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" 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" 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" target="_blank">#<span>RetroComputing</span></a> <a href="https://infosec.space/tags/Hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hardware</span></a> <a href="https://infosec.space/tags/Question" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Question</span></a> <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ix86</span></a> <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a></p>
Cory DoctorowLong thread/25