diff options
| author | Nicolas Piatto <nico@lodpp.net> | 2021-03-05 22:57:13 +0000 |
|---|---|---|
| committer | Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2021-03-06 11:11:53 +0700 |
| commit | 8805058fdfed520b8494f3fc9c1ffb6670bb889b (patch) | |
| tree | 00d06ad9f0edd2d7f676268bf63956d9093c269e /development/git-crypt/slack-desc | |
| parent | c399dd335d5adda2111b54ef2418606789adbba3 (diff) | |
development/git-crypt: Added (transparent file encryption in git)
Signed-off-by: Dave Woodfall <dave@slackbuilds.org>
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'development/git-crypt/slack-desc')
| -rw-r--r-- | development/git-crypt/slack-desc | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/development/git-crypt/slack-desc b/development/git-crypt/slack-desc new file mode 100644 index 0000000000..c7b4bd94f6 --- /dev/null +++ b/development/git-crypt/slack-desc @@ -0,0 +1,19 @@ +# HOW TO EDIT THIS FILE: +# The "handy ruler" below makes it easier to edit a package description. +# Line up the first '|' above the ':' following the base package name, and +# the '|' on the right side marks the last column you can put a character in. +# You must make exactly 11 lines for the formatting to be correct. It's also +# customary to leave one space after the ':' except on otherwise blank lines. + + |-----handy-ruler------------------------------------------------------| +git-crypt: git-crypt (transparent file encryption in git) +git-crypt: +git-crypt: git-crypt enables transparent encryption and decryption of files in a +git-crypt: a git repository. Files which you choose to protect are encrypted +git-crypt: when committed, and decrypted when checked out. git-crypt lets you +git-crypt: freely share a repository containing a mix of public and private +git-crypt: content. git-crypt gracefully degrades, so developers without the +git-crypt: secret key can still clone and commit to a repository with encrypted +git-crypt: files. This lets you store your secret material (such as keys or +git-crypt: passwords) in the same repository as your code, without requiring you +git-crypt: to lock down your entire repository |