Fixes #6

Also adds me to the contributors list - the CONTRIBUTING.md encourages it, but this is a really small change so it feels weird.

https://highassurance.rs/chp1/_index.html

Public content is not published yet (I have seen #4) so I can't open a PR for it, sorry :(

In the 12th footnote in currently published version of https://highassurance.rs/chp3/undef.html the link to ThreadSanitizer has a typo

Hello! I'm looking at https://highassurance.rs/chp7/traits.html#the-map-get-api.
The example with the get is never introducing the second generics K and V in the code example.

/// Returns a reference to the value corresponding to the key.
pub fn get<Q>(&self, key: &Q) -> Option<&V>
where
    K: Borrow<Q> + Ord,
    Q: Ord + ?Sized,
{
    // ...function body here...
}

I think a better example would be:

impl<K, V> BTreeMap<K, V> {
    pub fn get<Q>(&self, key: &Q) -> Option<&V>
    where
        K: Borrow<Q> + Ord,
        Q: Ord + ?Sized,
    {
        // ...function body here...
    }
    // ... rest of the methods
}

to show where the generic for BTreeMap are introduced. There is a mention of BTreeMap<K, V> but in my opinion I think it's easily missed and this would illustrate how the generics from the impl are used.

When running docker build . on the Dockerfile, the following errors occurs:

Just wondering if anyone else has run or is running into this issue?

In src/chp1/_hands_on.md, line 109:

[^Namespaces]: [*Everything You Need to Know about Linux Containers, Part II: Working with Linux Containers (LXC)*](https://code.visualstudio.com/docs/remote/containers). Petros Koutoupis (2018).

should be

[^Namespaces]: [*Everything You Need to Know about Linux Containers, Part II: Working with Linux Containers (LXC)*](https://www.linuxjournal.com/content/everything-you-need-know-about-linux-containers-part-ii-working-linux-containers-lxc). Petros Koutoupis (2018).

The original link is about containers, but about setting them up using an extension for VScode and doesn't have the given title.

For the v0.3.1 update (#4), I'd like to add a "Community Contributors" list to the current "About the Team" page of the book. The idea is to alphabetically list the GitHub usernames of eagle-eyed readers who spot typos and issue PRs, e.g:

• a_username
• b_username
• c_username

This could be a nice way to recognize community contributors for what might count as "proofreading" work in a traditional book publisher's process 👍

Will add a CONTRIBUTING.md with more details in the next few days. Then reach out to those who provided typo fixes via email to ask consent for retroactive addition to the list.

Much like software bugs, typos are difficult to detect automatically and at scale! Appreciate the manual effort and feel this could lead to a more polished book in the long-term.

In the C code here https://highassurance.rs/chp4/attack_1.html#breaking-temporal-memory-safety-value-validity,

    char* greeting = get_greeting();
    size_t greeting_len = strlen(greeting); // Excludes null byte  <-- Calling `strlen` before checking that greeting is non null
    if (greeting != NULL) {

We call strlen before checking that greeting is non-null, resulting in Undefined Behavior

is this project dead?

Coming ASAP:

• Address accumulated feedback (huge thanks to everyone who reached out!)
• Add PDF and EPUB downloads to the site (see #2)
• Add source for all public content to this repo in order to reduce friction for typo fixing (see #3)

In https://highassurance.rs/chp4/assure_stack_1.html#the-stack, the stack diagram show that the stack frame for the square function still exist under all the recursive_count_down stack frames.
https://github.com/tnballo/high-assurance-rust/blob/main/src/chp4/stack_example.svg

But in my understanding, the stack frame of square should pop before the stack frames of recursive_count_down are added.

Indeed if I print the backtrace with:

        println!("Boom!");
        println!("{:#?}", backtrace::Backtrace::capture());
        return x;

I get:

Backtrace [
    { fn: "stack_test::recursive_count_down", file: "./src/main.rs", line: 8 },
    { fn: "stack_test::recursive_count_down", file: "./src/main.rs", line: 13 },
    { fn: "stack_test::recursive_count_down", file: "./src/main.rs", line: 13 },
    { fn: "stack_test::recursive_count_down", file: "./src/main.rs", line: 13 },
    { fn: "stack_test::recursive_count_down", file: "./src/main.rs", line: 13 },
    { fn: "stack_test::main", file: "./src/main.rs", line: 35 },
...

Did I miss something ?

I have added pdf version of high assurance rust in https://github.com/shirshak55/Rust-Book-In-PDF/releases. Let me know if there is any issue.

In dynamic_assurance_2.md and dynamic_assurance_3.md, the path to rc4's lib.rs is written as crypto_tool/rc4/lib.rs, though cargo new crypto_tool/rc4 --lib creates lib.rs in crypto_tool/rc4/src/lib.rs

The sample above shows what happens when trying to save this to a pdf. Not sure the cause here but I plan to do more digging as I want to read this on my ereader with reasonable ease.

In the second sentence of this section, the book currently reads as

Rust can run in levels of the stack were scripting languages

... but the usage of "were" is incorrect. It should instead be

Rust can run in levels of the stack where scripting languages

As a side note, I would really appreciate if the book's source was present in this repository, even if you decide to keep it in some other branch for now - needing to open an issue or send an email is a bit irritating when one could instead just open a pull request to address an issue directly.