On 3/2/23 9:53 PM, efeizbudak wrote:
Doesn't this sort of defeat the purpose of using pass? I mean if it's
always decryptable then is it really useful to have it encrypted in the
first place (assuming you have full disk encryption set up)? I may be
missing something crucial here so please let me
Matt:
> I don't have any thoughts on the pam module, but I make use of some
> scripts that rely on pass as well. For my use case I just raised the
> TTL setting of gpg-agent to match an eight hour work day or eight hour
> evening period and ran with it. Feels fairly natural to "log in" to
> the a
Thanks
Dave
On Sun, Feb 19, 2023, 05:31 Neil Bothwick wrote:
> On Wed, 15 Feb 2023 23:09:54 -0500, Walter Dnes wrote:
>
> > > It's bad enough depclean deleting the active kernel if you don't
> > > watch out, without something deciding to install a non-existent
> > > kernel and deleting the live
On 3/2/23 6:48 AM, Matt Connell wrote:
You just described gpg-agent, the core of what Efe (OP) is meddling
with :)
No, I didn't.
I was referring to having the OP's utility read the password and
interact with GPG /once/ at startup and then the utility run for a much
longer time retaining the
On Wed, 2023-03-01 at 15:38 -0700, Grant Taylor wrote:
> Can you re-architect this as a (pseudo) daemon so that you unlock it
> once (or at least a LOT less often) and it stores the necessary
> information in memory for subsequent re-use?
You just described gpg-agent, the core of what Efe (OP) i
5 matches
Mail list logo
