|
1 |
| -<img src="icon.svg" width="64" alt/> Myba — git-based backup utility with encryption |
| 1 | +<img src="icon.svg" width="64" alt/> Myba — git-based backup with encryption |
2 | 2 | =====
|
3 | 3 |
|
4 | 4 | [](https://github.com/kernc/myba/actions)
|
|
14 | 14 | open-source, secure, distributed, version-controlled, encrypted
|
15 | 15 | file backup software based on `git`**,
|
16 | 16 | for **Linux, MacOS, BSDs**, and possibly even **Windows/WSL**.
|
17 |
| -In a world of vice, instability, evergreen browsers, fast-moving markets and near constant _supply chain attacks_, |
18 |
| -it's the best kind of backup utility—**a timeless shell script** that relies on few, well-tested and _stable_ technologies. |
| 17 | +In a world of vice, instability, "evergreen" browsers, fast-moving markets and near constant _supply chain attacks_, |
| 18 | +it's the only kind of backup—**a timeless shell script** that relies on few, well-tested, _stable_ technologies. |
19 | 19 | Its only **dependencies are**:
|
20 | 20 |
|
21 | 21 | * a running **shell** / standard **POSIX environment** (sh, bash, zsh, dash, ... WSL?),
|
22 | 22 | * **gzip**
|
23 | 23 | * **git** (and Git LFS for files sized >40 MB),
|
24 | 24 | * either **OpenSSL** (AES256-CTR) or **GPG** (AES256-CFB) for encryption,
|
25 | 25 |
|
26 |
| -all of which you should discover most popularly available. |
| 26 | +all of which you should find most popularly available. |
27 | 27 |
|
28 |
| -**Git does a great job of securely storing and tracking changes and backing up important documents,** |
29 |
| -it is popular and widely-deployed, |
30 |
| -[feature-rich](https://git-man-page-generator.lokaltog.net/), |
| 28 | +**Git does a great job of securely storing and tracking changes and backing up important documents.** |
| 29 | +It is popular, |
| 30 | +[feature-rich](https://git-man-page-generator.lokaltog.net/) and widely-deployed, |
31 | 31 | but it doesn't on its own support encryption, which might be important if the backed-up data
|
32 |
| -is going to be shared with untrusted (and untrustworthy) third parties |
33 |
| -and various intermediary data "processors". |
| 32 | +is going to be shared with untrusted (untrustworthy) third parties |
| 33 | +and their intermediary "data processors". |
34 | 34 | One _could_ most simply set up an encryption-decryption process
|
35 | 35 | consisting of [**`clean` and `smudge` git filters** issued pre commits and post checkouts](https://git-scm.com/book/ms/v2/Customizing-Git-Git-Attributes#filters_a),
|
36 |
| -respectively, but **git filters can't encrypt the tracked file paths / filenames**, |
| 36 | +respectively, but **git filters don't encrypt the tracked file paths / filenames**, |
37 | 37 | whereas one might have a want for that, otherwise almost what's the point? 😶
|
38 | 38 |
|
39 | 39 | Features
|
|
0 commit comments