Il 19/02/2016 15:17, Harman, Michael ha scritto:
> Thanks Brian. I think I tried this but I couldn’t figure out how to
> completely hide the passphrase so no one could get to it. Maybe I was
> using it incorrectly. Since this is an unattended operation that runs
> day and night, I wanted to secure
: Thursday, February 18, 2016 3:10 PM
To: Harman, Michael; gnupg-users@gnupg.org
Subject: Re: Use of --passphrase-file
A pretty good option is to use gpg-agent. It can keep your passphrase /secret
key in (secure) memory for a few minutes so you can use the key in scripted
tasks.
On Thu, Feb 18
. | a subsidiary of Universal Health Services | Phone
610.768.3416
From: Steve Butler [mailto:sbut...@fchn.com]
Sent: Thursday, February 18, 2016 2:56 PM
To: Harman, Michael; gnupg-users@gnupg.org
Subject: RE: Use of --passphrase-file
Any "secure" storage for the passphrase will itself n
A pretty good option is to use gpg-agent. It can keep your passphrase
/secret key in (secure) memory for a few minutes so you can use the key in
scripted tasks.
On Thu, Feb 18, 2016, 4:24 PM Harman, Michael
wrote:
> I am attempting to automate a process that decrypts files. The files are
> encry
Any "secure" storage for the passphrase will itself need a mechanism to
"unlock". This only digs the hole one more level down. Only you can decide
when to stop digging. But remember, whatever the automated script can do, a
human following the script can also do. [Note to self, use "hacker" i
