<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>OCI on Thorsten Hans</title>
		<link>https://thorsten-hans.com/tags/oci/</link>
		<description>Recent content in OCI on Thorsten Hans</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 02 Nov 2021 14:19:39 +0000</lastBuildDate>
		
			<atom:link href="https://thorsten-hans.com/tags/oci/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Distribute WebAssembly modules as OCI artifacts</title>
				<link>https://thorsten-hans.com/distribute-webassembly-modules-as-oci-artifacts/</link>
				<pubDate>Tue, 02 Nov 2021 14:19:39 +0000</pubDate>
				<guid>https://thorsten-hans.com/distribute-webassembly-modules-as-oci-artifacts/</guid>
				<description>&lt;p&gt;When using WebAssembly (Wasm) on platforms different than the browser, we have to care about distribution. How can we securely transfer our Wasm modules to desired environments? How can we verify integrity to ensure Wasm modules were not compromised during distribution?&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s take a look at the container world. Container registries (those that implement the Docker Registry 2.0 standard (or to be more precise, the &lt;a href=&#34;https://github.com/opencontainers/distribution-spec&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;OCI distribution spec&lt;/a&gt;&#xA;)) are a trusted distribution channel that addresses all the questions raised before. This does not mean that we have to package our Wasm modules as containers! Container registries can store and distribute more than just containers. Container registries can store any OCI compliant artifact. And that&amp;rsquo;s exactly what we will create from our Wasm modules to leverage container registries as a trusted distribution channel.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
