I'm looking for some help explaining the behavior of gpg-preset-passphrase.
First, the manpage states:
Passphrases set with this utility don't expire unless the
--forget
option is used to explicitly clear them from the cache --- or
gpg-agent
is either restarted or reloade
I know it's sort of a contradiction in terms, but hear me out:
The case I'm looking at is a High Availability environment hosting a
database. The database is comprised of many Unix files, encrypted via AES,
on shared storage. If the node accessing the database loses enough of its
redundant hardwar
On Thu, Mar 18, 2010 at 10:37 AM, Grant Olson wrote:
> On 3/18/2010 7:50 AM, Daniel Eggleston wrote:
> > ..., with the ultimate goal
> > that if somebody does somehow walk out with the storage containing the
> > databases, there will be no way to gain access to the data.
&g
Yea, I don't need to have it entered automatically at boot time (if that's
possible, I've just thrown all semblance of true security out the window).
All I was looking for is a way to have gpg cache the passphrase for an
indefinite amount of time; and a human can enter the passphrase at boot.
It s
On Tue, May 25, 2010 at 10:03:30AM -0400, Jeremy Bennett wrote:
>I have been googling for an answer on how to have gpg encrypt a file to a
>file with a pgp extension. It looks like maybe the only way is via a
>output redirect (> ?). I'm trying this via a command line on a windows
>
On Sun, 30 May 2010 00:58:57 + (UTC)
"Michael D. Berger" wrote:
> On Sat, 29 May 2010 19:46:29 -0500, John Clizbe wrote:
>
> > Michael D. Berger wrote:
> >> On a Linux box, in encrypting a file with gpg, I get this query:
> >>
> >>It is NOT certain that the key belongs to the person nam
