Well I've made things slightly more batshitinsane and added support for reencrypting the password when it gets to its destination. While I was at it, I added copy, since when copying things into a new folder, we need reencryption to occur too, which means the normal file system tools become insufficient, which means... Which means ugh.
Which means this is why I held off on implementing "team pass" for so long, because I knew it would necessitate tools like "pass mv" and "pass cp" to be "complete", and well, here we are, and now they're there. http://git.zx2c4.com/password-store/commit/?id=586f6bd1eb32766168645d0582839dbf36e7f205 So, ugh. I've written it; it's there; it should be mostly debugged (BUT I'M SURE I SCREWED UP SO PLEASE STRESS TEST IT). But do we actually want this? On one hand, it's additional file-manager bloat that pass is supposed to avoid in the first place. On the other hand, it becomes very handy when using team pass, such as, "pass cp Managers/website Sysadmin/website", or "pass mv OriginalSubcontractor/website NewSubcontractor/website", since it takes care of the reencryption when different subdirectories have different .gpg-id files. I'm torn. _______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
