I went to hack on brackup after a long break, and it bitches at me now. Or rather, gpg does:
sammy:trunk $ ./brackup --from=brackup --to=amazon \
gpg: 92FDF929: There is no assurance this key belongs to the named user
pub 4096g/92FDF929 2006-03-20 Brad Fitzpatrick <email@example.com>
Primary key fingerprint: E5C8 295F D1AB 7DE1 C5DF 7F68 FB52 E360 5E1B 3EC5
Subkey fingerprint: B269 19C9 1BAD 3458 7B9A B888 B9C6 667B 92FD F929
It is NOT certain that the key belongs to the person named
in the user ID. If you *really* know what you are doing,
you may answer the next question with yes.
Use this key anyway? (y/N)
That's new. I must've upgraded.
Where's the --just-do-what-i-fucking-say option?
"--recipient", $gpg_rcpt, "--encrypt", "--output=$etmpfn", "--yes", $tmpfn)
and die "Failed to run gpg: $!\n";
Note the --yes. Apparently that means --unless-you-feel-bitchy-in-this-new-ver
Context switch time. No love for Brackup because gpg is full of hate.