4 ms·

First of all: Thank you for pass! We've been using it a lot internally and just because pass is so awesome, we decided to start gopass. We use Go for almost ev

First of all: Thank you for pass! We've been using it a lot internally and just because pass is so awesome, we decided to start gopass. We use Go for almost everything at JustWatch and that's why we decided to rewrite it in Go as this would allow us to add even more features with better abstraction in the future. Bash just didn't feel like the right fit for that.

benologist 10y ago
That's exciting, because now we get to find out how big a problem is a tool you use being in a language you don't. It might actually be a good idea if the original one is waning cause you only need to make a competitive version of any one of those tools or businesses.
gmluke 10y ago
I looked at the code for pass recently, and thought it was a nice example of something where bash is absolutely adequate. You point out (in discussing the design of pass): > There is one slight drawback to all the simplicity, and that is an information disclosure inherent to the design: pass stores all folder and file names in clear text, so even if you fully trust GPG, you should probably not put this repo into a public place like Github, because this may expose your account names and other metadata. What's not completely obvious from a cursory read is whether gopass improves upon that. Also, the multiple stores feature looks like it might be quite nice, but a lengthier example would be very helpful! Edit: improve clarity
- johnnycarcin 10y ago
  I was just thinking the same thing and was wondering if I missed that? I have been working on a similar project for keeping bookmarks and haven't found (yet) an easy way to obfuscate directory and file names in a way that doesn't make the tree structure look like a mess but still makes it difficult for the majority of people to "crack".

4 ms·

First of all: Thank you for pass! We've been using it a lot internally and just because pass is so awesome, we decided to start gopass. We use Go for almost ev

by MetalMatze 10y ago

benologist 10y ago
That's exciting, because now we get to find out how big a problem is a tool you use being in a language you don't. It might actually be a good idea if the original one is waning cause you only need to make a competitive version of any one of those tools or businesses.
gmluke 10y ago
I looked at the code for pass recently, and thought it was a nice example of something where bash is absolutely adequate. You point out (in discussing the design of pass): > There is one slight drawback to all the simplicity, and that is an information disclosure inherent to the design: pass stores all folder and file names in clear text, so even if you fully trust GPG, you should probably not put this repo into a public place like Github, because this may expose your account names and other metadata. What's not completely obvious from a cursory read is whether gopass improves upon that. Also, the multiple stores feature looks like it might be quite nice, but a lengthier example would be very helpful! Edit: improve clarity
- johnnycarcin 10y ago
  I was just thinking the same thing and was wondering if I missed that? I have been working on a similar project for keeping bookmarks and haven't found (yet) an easy way to obfuscate directory and file names in a way that doesn't make the tree structure look like a mess but still makes it difficult for the majority of people to "crack".