On 2019-01-15 21:58:37, Aleksei Fedotov wrote:
Git would have not protected you from the case you described, but it
protects you from losing data and makes all changes traceable and
reversible.
I think it would have, because it makes the commit when you close the=20
editor.
So the password he
On Tue, Jan 15, 2019 at 09:58:37PM +0100, Aleksei Fedotov wrote:
> If you store your passwords in a Git repository, they are automatically
> tracked by pass. Any edits are committed to the repository and any
> accidental changes could be reverted.
Yeah, I use GIT all the time for software
On Tue, Jan 15, 2019 at 03:26:52PM -0500, Joshua N Pritikin wrote:
> At the beginning of "pass edit foo", would it be possible to snapshot
> the previous version of the file? Then if the file didn't match it's
> snapshot, the user could be warned.
Do you have your password store under git?
On January 15, 2019 12:41:37 PM PST, Joshua N Pritikin
wrote:
>On Tue, Jan 15, 2019 at 09:34:14PM +0100, Tobias Girstmair wrote:
>> if you're using git there should* be a commit added for each change.
>type
>> 'pass git log' to verify if there are two entries for 'foo' (i.e.
>"Edit
>>
On Tue, Jan 15, 2019 at 09:34:14PM +0100, Tobias Girstmair wrote:
> if you're using git there should* be a commit added for each change. type
> 'pass git log' to verify if there are two entries for 'foo' (i.e. "Edit
> password for foo using vim."), and if that's the case, undo the latest
>
if you're using git there should* be a commit added for each change.
type 'pass git log' to verify if there are two entries for 'foo' (i.e.
"Edit password for foo using vim."), and if that's the case, undo the
latest commit with 'pass git revert HEAD~1'.
lg
* famous last words
On Tue,
