Re: [pass] Password age report

nope, not necessary - take a look at your .gitattributes: git diff will use gpg for decrpytion before diffing. pass sets it up that way for you ;) On 01.09.2016 11:39, Simon Lackerbauer wrote: > Well, don't forget to send it through pass first to decrypt, like > > date -d @$(pass git blame -L

Re: [pass] Password age report

pass integrates with git blame for plaintext comparison. if you can still decrypt older entries, this should give you exact change dates. try something like date -d @$(git blame -L 1,1 --porcelain dropbox.com.gpg | sed -n 's/^committer-time //p') (taken from this mail on the mailing list:

Re: [pass] Password age report

On 31.08.2016 19:02, Kjetil Torgrim Homme wrote: > Den 31. aug. 2016 17:48, Brian Candler skreiv: >> On 31/08/2016 16:43, Emile Cantin wrote: >>> In light of the recent Dropbox leak, I wanted to know how old my >>> password was, and perhaps if I had any other old passwords that would >>> be due

Re: [pass] Password age report

Den 31. aug. 2016 17:48, Brian Candler skreiv: > On 31/08/2016 16:43, Emile Cantin wrote: >> >> In light of the recent Dropbox leak, I wanted to know how old my >> password was, and perhaps if I had any other old passwords that would >> be due for a rotation. I don't think I can rely on the last

Re: [pass] Password age report

I currently sign my git commits, but signing the original files would be even better, I guess. It always felt weird for me that I was able to write to the store without my secret key. Le mer. 31 août 2016 à 11:48, Brian Candler a écrit : > On 31/08/2016 16:43, Emile Cantin