<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in security.md</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>bac0e78f - aarch64: Disable csdb emission by default (#12932)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/security.md#bac0e78f</link>
        <description>aarch64: Disable csdb emission by default (#12932)* aarch64: Disable csdb emission by defaultThis has a massive performance penalty on macOS, for example, and peercompilers are not emitting this as part of on-by-default mitigations.This commit preserves the option to emit it with an aarch64-specific`use_csdb` flag, but the default is now `false` meaning that this is notemitted by default.Closes #12789* Fix tests* Fix tests &amp; review comments* Use ISLE rule introduced

            List of files:
            /wasmtime-44.0.1/docs/security.md</description>
        <pubDate>Wed, 01 Apr 2026 22:16:55 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>0e9121da - Fix some typos (#8641)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/security.md#0e9121da</link>
        <description>Fix some typos (#8641)* occurred* winch typos* tests typos* cli typos* fuzz typos* examples typos* docs typos* crates/wasmtime typos* crates/environ typos* crates/cranelift typos* crates/test-programs typos* crates/c-api typos* crates/cache typos* crates other typos* cranelift/codegen/src/isa typos* cranelift/codegen/src other typos* cranelift/codegen other typos* cranelift other typos* ci js typo* .github workflows typo* RELEASES typo* Fix clang-format documentation line---------Co-authored-by: Andrew Brown &lt;andrew.brown@intel.com&gt;

            List of files:
            /wasmtime-44.0.1/docs/security.md</description>
        <pubDate>Thu, 16 May 2024 23:21:22 +0000</pubDate>
        <dc:creator>FrankReh &lt;FrankReh@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>0ee66411 - Bring some of Wasmtime&apos;s documentation more up-to-date (#6994)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/security.md#0ee66411</link>
        <description>Bring some of Wasmtime&apos;s documentation more up-to-date (#6994)* Remove tutorial/wasm-writing documentationThis commit removes the tutorial and &quot;Writing WebAssembly&quot; documentationsections from Wasmtime&apos;s documentation. These sections are quite datedat this point (they still recommend `cargo wasi`!) and haven&apos;t beenupdated much since their inception, especially in the arena ofcomponents. Today it seems best to leave this sort of documentation to[other resources] which are more tailored towards documentation ofwriting wasm.[other resources]: https://component-model.bytecodealliance.org/* Remove markdown example from docsLike the previous commit this is quite dated and recommendseffectively-deprecated tooling and doesn&apos;t take into account components.* Update our intro docs a bit* Link security blog post from docs* Fold docs of wasm proposals into tier docsThis was already a bit duplicated so consolidate into one location.Additionally add some proposals that weren&apos;t previously documented andmove some around based on their implementation status.* Document unsupported featuresIn an effort to head off questions about platform support I figure itmight be a good idea to start documenting what&apos;s not supported at thistime. This is intended to mirror the current state, not future, ofWasmtime. In other words this should answer the question of &quot;DoesWasmtime support X?&quot; as opposed to &quot;Does Wasmtime want to support X?&quot;since we want to eventually support all of these features in the limit.* Fold WASI docs into tier docsSimilar to the previous commit but for WASI proposals.

            List of files:
            /wasmtime-44.0.1/docs/security.md</description>
        <pubDate>Mon, 11 Sep 2023 16:56:12 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>a75f383f - Improve the `wasmtime` crate&apos;s README (#4174)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/security.md#a75f383f</link>
        <description>Improve the `wasmtime` crate&apos;s README (#4174)* Improve the `wasmtime` crate&apos;s READMEThis commit is me finally getting back to #2688 and improving the READMEof the `wasmtime` crate. Currently we have a [pretty drab README][drab]that doesn&apos;t really convey what we want about Wasmtime.While I was doing this I opted to update the feature list of Wasmtime aswell in the main README (which is mirrored into the crate readme),namely adding a bullet point for &quot;secure&quot; which I felt was missingrelative to how we think about Wasmtime.Naturally there&apos;s a lot of ways to paint this shed, so feedback is ofcourse welcome on this! (I&apos;m not the best writer myself)[drab]: https://crates.io/crates/wasmtime/0.37.0* Expand the &quot;Fast&quot; bullet a bit more* Reference the book from the wasmtime crate* Update more security docsAlso merge the sandboxing security page with the main security page toavoid the empty security page.

            List of files:
            /wasmtime-44.0.1/docs/security.md</description>
        <pubDate>Fri, 20 May 2022 20:33:00 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>3b3b126f - Refer to BA security policy (#2912)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/security.md#3b3b126f</link>
        <description>Refer to BA security policy (#2912)

            List of files:
            /wasmtime-44.0.1/docs/security.md</description>
        <pubDate>Wed, 19 May 2021 16:24:42 +0000</pubDate>
        <dc:creator>Till Schneidereit &lt;till@tillschneidereit.net&gt;</dc:creator>
    </item>
<item>
        <title>bf526b62 - Add book documentation skeleton and auto-publish from CI (#435)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/security.md#bf526b62</link>
        <description>Add book documentation skeleton and auto-publish from CI (#435)This commit adds the skeleton of a new set of documentation for`wasmtime` in the existing `docs` directory. This documentation isorganized and compiled with [mdbook] which the Rust project uses formost of its own documentation as well. At a previous meeting webrainstormed a rough skeleton of what the documentation in this bookwould look like, and I&apos;ve transcribed that here for an example of howthis is rendered and how it can be laid out. No actual documentation iswritten yet.This commit also additionally adds necessary support to auto-publishboth this book documentation and API documentation every time a commitis pushed to the `master` branch. All HTML will be automatically pushedto the `gh-pages` branch so long as the CI passes, and this should getdeployed to https://cranestation.github.io/wasmtime.I&apos;ve done a few dry-runs and I think this&apos;ll all work, but we&apos;ll likelytweak a few things here and there after running this through CI to makesure everything looks just as we&apos;d like. My hope though is that afterthis lands we can start actually filling out all the documentation andbeing able to review it as well.[mdbook]: https://crates.io/crates/mdbook

            List of files:
            /wasmtime-44.0.1/docs/security.md</description>
        <pubDate>Tue, 29 Oct 2019 14:55:51 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
