Signing with GnuPG:
$ gpg --sign --armor \ --output resolution-001.md.github_handle.asc \ resolution-001.md
$ keybase pgp sign \ --infile resolution-001.md \ --outfile resolution-001.md.github_handle.asc
Verifying with GnuPG:
$ gpg --verify resolution-001.md.github_handle.asc
$ keybase pgp verify \ --infile resolution-001.md.github_handle.asc
The text of the signed document is embedded in the signature file, so you can drop any signature file
resolution-XXX.md.github_handle.asc into keybase.io/verify to verify a signature.
For example, you can try verifying resolution-001.md.benhylau.asc.
Note: for submitting resolutions to the Government, you will need to use an additional signing process as if resolutions are external documents. Previously this was achieved by using
pandoc to build a PDF package with the resolution (without including PGP signatures) and entering that to HelloSign (see organizing/#385 for context).
Members also use other tools such as HelloSign for signing client-facing documents.
See this related GitHub issue for an example of prior usage.