| Age | Commit message (Collapse) | Author |
|---|
|
The framework expects to be able to ignore specific exit codes from the
plugins, but if we are possibly returning exit codes from different
tools, then it's hard to untangle what tool generated which exit code.
In the plugins at hand the exit code 1 seems like a safe one, given both
curl and rsync usage, so we currently turn any OpenPGP verification
error into that.
|
|
Otherwise we get the following error:
gpgv: no signed data
gpgv: can't hash datafile: No data
|
|
These are OpenPGP signatures that any conforming implementation should
be able to handle. They are not specific to GnuPG, which is one of many
implementations, even though a very prominent one.
|
|
|
|
|
|
Thanks: Philipp Kern <pkern@debian.org>
|
|
+ add SSL verification options
+ replace PGCLUSTER with PGHOST, former cements the use of a specific
version of postgresql-client.
Git-Dch: Full
|
|
|
|
|
|
|
