Skip to content

Latest commit

 

History

History
66 lines (46 loc) · 1.78 KB

SIGNED.md

File metadata and controls

66 lines (46 loc) · 1.78 KB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQBUMoVnIw5BvwqM8ugRAnvoAJ9e8FncrrnhSuMyFZ66FLGqKtE0UACgsTlf
yUtjrXYQWen0sHApHIYLbJ4=
=ynVi
-----END PGP SIGNATURE-----

Begin signed statement

Expect

size   exec  file          contents                                                        
             ./                                                                            
1083           LICENSE     4178033099aaf70f243ee900b5efdcd63d580d3f06b1b75356786ccedcc4045e
9348           README.md   a6b6c47d4ebca77bd94b9809df2b9bfa4995ea6c746275a9774c9fea0991accd
1269           install.sh  2586247475de27699b513acb39399ecf69d58b0ad5706c23f490ddafc3397c0a
12611  x       rbbedit     d2f48ed034b1fd1a7bbb39f95d68701ee480210d26dbd432b6448ebdf4c20347

Ignore

/SIGNED.md

Presets

git      # ignore .git and anything as described by .gitignore files
dropbox  # ignore .dropbox-cache and other Dropbox-related files    
kb       # ignore anything as described by .kbignore files          

End signed statement


Notes

With keybase you can sign any directory's contents, whether it's a git repo, source code distribution, or a personal documents folder. It aims to replace the drudgery of:

  1. comparing a zipped file to a detached statement
  2. downloading a public key
  3. confirming it is in fact the author's by reviewing public statements they've made, using it

All in one simple command:

keybase dir verify

There are lots of options, including assertions for automating your checks.

For more info, check out https://keybase.io/docs/command_line/code_signing