Angel, I came to that realization as I worked through with your guidance, the configuration I wanted. Technology, while here to help, can be a drawback at times. Or perhaps better said, has its own limitations.
Many thanks and stay safe. Dave -----Original Message----- From: Gnupg-users <gnupg-users-boun...@gnupg.org> On Behalf Of Ángel Sent: Friday, December 18, 2020 3:50 PM To: gnupg-users@gnupg.org Subject: Re: GPG Decrypt Error based on a timeout function? On 2020-12-18 at 10:25 -0800, Dave via Gnupg-users wrote: > Angel, > Yes, I want the script to run unattended, which the gpg process is > not the right method, as you say: " you could configure the gpg > password in the script, but then that would be roughly equivalent to > the email account password." > > Many thanks and stay safe and healthy, Dave You cannot make a machine which needs a secret run fully unattended without having such secret *somewhere*. You can move pieces around, separate roles amongst different parts, protect a secret in a way that a _different_ secret is needed instead, etc. But in the end, as the machine needs that secret, you need to store it there. Or, alternatively, have a human input it and have it stored in memory, with the caveat that the machine won't be able to boot to a fully functional state until that is provided. _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users