diff options
| author | Georg Koppen <gk@torproject.org> | 2021-06-11 10:01:14 +0000 |
|---|---|---|
| committer | Rasmus Dahlberg <rasmus.dahlberg@kau.se> | 2021-06-11 13:15:51 +0200 |
| commit | bbd8a6b529fb4ed4ea93b827af462a735b950492 (patch) | |
| tree | b73138b7d2a41e138f7ecac46b7a662b761911a4 | |
| parent | ade8b8dacbeab225362a93f94fbc56e6c687bc0f (diff) | |
Fix typo
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -23,7 +23,7 @@ you know that your signing infrastructure was compromised at some point. The same goes for binaries that show up for download on your website but don't have a corresponding log entry. Anyone can also detect if a logged checksum is unaccounted for in your package repository or a binary on your website is -missing a corresponing log entry just by inspecting the log. In other words, +missing a corresponding log entry just by inspecting the log. In other words, the claim that the same binaries are published for everyone can be _verified_. Adding signed checksums into a log is already an improvement without any |