~aman/static-mozjpeg

4f3105d8751968781edf75102e713e90567d7b93 — Aman Verma 2 months ago c61186f
Update readme.
1 files changed, 3 insertions(+), 3 deletions(-)

M README.md
M README.md => README.md +3 -3
@@ 15,15 15,15 @@ compare the public keys from at least 2 different places and make sure they are
identical. If they aren't, that could mean one of my accounts has been hacked.
Finally, run

    signify -C -p <pubkey> -x SHA256SUMS.sig
    signify -C -p <pubkey> -x [possible prefix]SHA256SUMS.sig

where `<pubkey>` is the public key file you downloaded and cross-checked earlier. If
you downloaded all the attached executables, you should get

    Signature Verified
    {filename}: OK
    <filename>: OK

where `{filename}` is the name of the file(s) you are trying to verify.
where `<filename>` is the name of the file(s) you are trying to verify.
If you didn't download all the attached executables, signify will complain with the word
"FAIL" after the filename, but it will still try to verify the ones that exist. If you see
"FAIL" after the name of a file that _does_ exist, or if you see "signify: signature