<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Can we solve this by building trustworthy systems out of untrustworthy parts?</title>
	<atom:link href="https://www.isegoria.net/2019/10/can-we-solve-this-by-building-trustworthy-systems-out-of-untrustworthy-parts/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.isegoria.net/2019/10/can-we-solve-this-by-building-trustworthy-systems-out-of-untrustworthy-parts/</link>
	<description>From the ancient Greek for equality in freedom of speech; an eclectic mix of thoughts, large and small</description>
	<lastBuildDate>Thu, 28 May 2026 23:08:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6.1</generator>
	<item>
		<title>By: CVLR</title>
		<link>https://www.isegoria.net/2019/10/can-we-solve-this-by-building-trustworthy-systems-out-of-untrustworthy-parts/comment-page-1/#comment-2981265</link>
		<dc:creator>CVLR</dc:creator>
		<pubDate>Sat, 05 Oct 2019 19:47:49 +0000</pubDate>
		<guid isPermaLink="false">https://www.isegoria.net/?p=45642#comment-2981265</guid>
		<description><![CDATA[I think about this a lot and I’ve developed a few ideas. It comes down to the wholesale, &lt;i&gt;in situ&lt;/i&gt; replacement of the “engineering” culture we currently have. 

Here are some technical points:

* The network connection is the critical chokepoint. An unsecure (sic) airgapped computer is almost as good (possibly as good as) a secure networked computer.

* Increasingly, computers are more and more specialized, which is to say, less and less general-purpose. With a decrease in general-purposeness comes a decrease in the scope of things that it must be &lt;i&gt;possible&lt;/i&gt; for a networked device to transmit for its effective operation.

* Therefore, it becomes practical to restrict the lifetime communications of some device to a predefined schema set at manufacture time. (Think along the lines of GraphQL.) SEARS once provided legendary schematics for its products; there is no reason for an interested layman of moderately above-average intelligence to be denied access to a document providing a comprehensive description of his device’s capabilities.

* Furthermore, the network connection can be cleanly extracted from the main system, and should be so. It can run on its own hardware; reside on read-only memory; be written in Haskell. If a device needs more comms than it currently possesses, its manufacturer can issue a microSD-card-like “flash” update. Between real costs to updates and a rigorous-though-not-prohibitive certification process, it will be uneconomical to issue half-baked software. To become a certifier must be a grueling process, within grasp only for the elite of the elite, and the profession’s pay pegged at a minimum of 5X the pay of a similar position in the private sector. The return on investment will be in excess of 100X.

* TH3. (GOTO: SQLite)

* Physical hardware switches for every sensor and wireless antenna. You flip open your smartphone, the microphone activates. You press a small toggle button, the camera turns on. Your flip your smartphone closed, it becomes a pager: capable of receiving calls and notifications, incapable of transmitting data, including geomatical information.

* Facebook, Instagram, Twitter, Snapchat, et al. should’ve been protocols; they aren’t, because in such a world the founders wouldn’t be billionaires and the world’s privacy wouldn’t be flooding into their datacenters. Similarly, with contemporary inexpensive, powerful, and energy-efficient hardware, it’s eminently possible, bordering on trivial, to design a “home cloud” distributed network of interoperable devices, sensibly firewalled from the Internet (see above). It hasn’t happened, for similar reasons.

These are not, as some would have you believe, insurmountable problems.]]></description>
		<content:encoded><![CDATA[<p>I think about this a lot and I’ve developed a few ideas. It comes down to the wholesale, <i>in situ</i> replacement of the “engineering” culture we currently have. </p>
<p>Here are some technical points:</p>
<p>* The network connection is the critical chokepoint. An unsecure (sic) airgapped computer is almost as good (possibly as good as) a secure networked computer.</p>
<p>* Increasingly, computers are more and more specialized, which is to say, less and less general-purpose. With a decrease in general-purposeness comes a decrease in the scope of things that it must be <i>possible</i> for a networked device to transmit for its effective operation.</p>
<p>* Therefore, it becomes practical to restrict the lifetime communications of some device to a predefined schema set at manufacture time. (Think along the lines of GraphQL.) SEARS once provided legendary schematics for its products; there is no reason for an interested layman of moderately above-average intelligence to be denied access to a document providing a comprehensive description of his device’s capabilities.</p>
<p>* Furthermore, the network connection can be cleanly extracted from the main system, and should be so. It can run on its own hardware; reside on read-only memory; be written in Haskell. If a device needs more comms than it currently possesses, its manufacturer can issue a microSD-card-like “flash” update. Between real costs to updates and a rigorous-though-not-prohibitive certification process, it will be uneconomical to issue half-baked software. To become a certifier must be a grueling process, within grasp only for the elite of the elite, and the profession’s pay pegged at a minimum of 5X the pay of a similar position in the private sector. The return on investment will be in excess of 100X.</p>
<p>* TH3. (GOTO: SQLite)</p>
<p>* Physical hardware switches for every sensor and wireless antenna. You flip open your smartphone, the microphone activates. You press a small toggle button, the camera turns on. Your flip your smartphone closed, it becomes a pager: capable of receiving calls and notifications, incapable of transmitting data, including geomatical information.</p>
<p>* Facebook, Instagram, Twitter, Snapchat, et al. should’ve been protocols; they aren’t, because in such a world the founders wouldn’t be billionaires and the world’s privacy wouldn’t be flooding into their datacenters. Similarly, with contemporary inexpensive, powerful, and energy-efficient hardware, it’s eminently possible, bordering on trivial, to design a “home cloud” distributed network of interoperable devices, sensibly firewalled from the Internet (see above). It hasn’t happened, for similar reasons.</p>
<p>These are not, as some would have you believe, insurmountable problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TRX</title>
		<link>https://www.isegoria.net/2019/10/can-we-solve-this-by-building-trustworthy-systems-out-of-untrustworthy-parts/comment-page-1/#comment-2980942</link>
		<dc:creator>TRX</dc:creator>
		<pubDate>Thu, 03 Oct 2019 17:30:42 +0000</pubDate>
		<guid isPermaLink="false">https://www.isegoria.net/?p=45642#comment-2980942</guid>
		<description><![CDATA[I remember a similar furor over putting RFID chips in US passports.  We &lt;em&gt;must&lt;/em&gt; have RFID chips in our passports, &lt;em&gt;now&lt;/em&gt;!  Even though they introduced a whole new security hole since they were remotely readable and cloneable...

Similarly, we &lt;em&gt;must&lt;/em&gt; have 5G networking &lt;em&gt;now&lt;/em&gt; because... we need to bump up our sales by forcing the purchase of new hardware?]]></description>
		<content:encoded><![CDATA[<p>I remember a similar furor over putting RFID chips in US passports.  We <em>must</em> have RFID chips in our passports, <em>now</em>!  Even though they introduced a whole new security hole since they were remotely readable and cloneable&#8230;</p>
<p>Similarly, we <em>must</em> have 5G networking <em>now</em> because&#8230; we need to bump up our sales by forcing the purchase of new hardware?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham</title>
		<link>https://www.isegoria.net/2019/10/can-we-solve-this-by-building-trustworthy-systems-out-of-untrustworthy-parts/comment-page-1/#comment-2980819</link>
		<dc:creator>Graham</dc:creator>
		<pubDate>Wed, 02 Oct 2019 20:57:19 +0000</pubDate>
		<guid isPermaLink="false">https://www.isegoria.net/?p=45642#comment-2980819</guid>
		<description><![CDATA[Or start peppering one&#039;s discourse with gratuitous insults against China. Or subtly backhanded praise. Or both. Keep em guessing, and try to use as many local or regional idioms and colloquialisms as possible.]]></description>
		<content:encoded><![CDATA[<p>Or start peppering one&#8217;s discourse with gratuitous insults against China. Or subtly backhanded praise. Or both. Keep em guessing, and try to use as many local or regional idioms and colloquialisms as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adar</title>
		<link>https://www.isegoria.net/2019/10/can-we-solve-this-by-building-trustworthy-systems-out-of-untrustworthy-parts/comment-page-1/#comment-2980790</link>
		<dc:creator>Adar</dc:creator>
		<pubDate>Wed, 02 Oct 2019 16:31:39 +0000</pubDate>
		<guid isPermaLink="false">https://www.isegoria.net/?p=45642#comment-2980790</guid>
		<description><![CDATA[Just stop using the telephone.]]></description>
		<content:encoded><![CDATA[<p>Just stop using the telephone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
