Skip to content

A backdoor to your letters #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

A backdoor to your letters #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ capabilities.
### Preparing retroactive reviews

Since "reading the source code" requires advanced domain knowledge, this
section describes a pen-and-paper aproach that can be used to cryptographically
section describes a pen-and-paper approach that can be used to cryptographically
ensure you can retro-actively review what you executed, even if you didn't
review before you executed it. Pen-and-paper should be taken literally here to
ensure this can't be modified by software. If done correctly, you don't need to
Expand Down
4 changes: 2 additions & 2 deletions writeups/dockerfile.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,12 @@ The Dockerfile has two stages, the first one compiles the source code:
folder that we're going to compile in and change the working directory to
this folder.
- `COPY . .` This copies the content of the current directory of the build
system into the container. The current dirctory on the build system is
system into the container. The current directory on the build system is
expected to be the folder that this repository was cloned to, so the files
that are copied are only those from the git repository.
- `RUN cargo build --release --locked --target=x86_64-unknown-linux-musl` This
compiles the rust source code into a binary. The command is explained in
detail in the [`Makefile`](makefile.md) writeup. This commnand is likely making our temporary
detail in the [`Makefile`](makefile.md) writeup. This command is likely making our temporary

The temporary build image is done at this point, the second `FROM` starts a new
image:
Expand Down