Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison to git-crypt #15

Open
t3hmrman opened this issue Sep 10, 2018 · 2 comments
Open

Comparison to git-crypt #15

t3hmrman opened this issue Sep 10, 2018 · 2 comments
Labels
documentation markdown documentation, in-line CLI documenatation help wanted

Comments

@t3hmrman
Copy link
Contributor

It would be nice if the documentation would how sheesy differentiates itself from a git-crypt.

So far as I can see currently:

  • No integration with git
  • No support for simple AES key encryption

Maybe it doesn't make sense to compare sheesy to a tool like git-crypt in the first place, since the scopes are somewhat different, if so I apologize! I think that sheezy could be super useful for storing secrets right in git repos so that's one way I really want to use it.

P.S. I just saw the talk @ RustCologne -- cool project!

@Byron Byron added documentation markdown documentation, in-line CLI documenatation help wanted labels Sep 11, 2018
@Byron
Copy link
Collaborator

Byron commented Sep 11, 2018

Indeed, and I agree that it would be nice to have. The reason it's not there yet is that I have never even looked at the tool.
From what I see, the bullet points provided here seem accurate, maybe there is more.

With the hopes of you getting more familiar with sheesy, maybe you would be able to deliver a comparison at some point.

@t3hmrman
Copy link
Contributor Author

t3hmrman commented Sep 11, 2018

I would love to contribute documentation on it! As soon as I find a free weekend I'll send a PR! :)

[EDIT] - Oh one thing, just for the future -- are you open to allowing simple AES keys rather than just PGP? It's cool if you're not but just figured I might ask

[EDIT2] - Ah, looking at lib/vault/src/recipients/add.rs it looks like GPG is pretty "in there", so to speak. Again I don't think it's a huge differentiator (one could easily just create a throwaway GPG keys), so that's fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation markdown documentation, in-line CLI documenatation help wanted
Projects
None yet
Development

No branches or pull requests

2 participants