Closed damaestro closed 10 years ago
As long as the files you'd like to encrypt have been staged (via git add <filename>
), they will show up when you run git ls-crypt
. After they have been committed, you can also validate that they are encrypted by looking at their raw form with:
$ git show HEAD:<path-to-file> --no-textconv
Why not add some shorthand in transcrypt?
transcrypt check path/to/file -> git show HEAD:path/to/file --no-textconv transcrypt ls -> git ls-crypt
Technically transcrypt doesn't have to remain installed on the machine after you've initialized a repository, but I could add some convenience options like:
-l, --list
list all of the currently encrypted files in the repository
-s, --show-raw=FILE
show the raw file as stored in the git commit object;
use this to check if files are encrypted as expected
That would be awesome. Possibly adding into the help what git commands are being ran under the hood.
I've added these two command line options and cut a new release version (that also has some bug fixes in there): v0.9.6. The Bash completion for --show-raw
was a lot trickier than I thought it would be, especially accounting for OS X only having Bash 3 and not Bash 4, so please do test that out and let me know if there are any issues.
It would be nice to be able to ask transcrypt what files are configured to be encrypted.