diff options
| author | Lars Wirzenius <liw@liw.fi> | 2015-03-24 20:25:33 +0200 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2015-03-24 20:25:33 +0200 |
| commit | 85554d3567f2b00dad4b97b1cfd2dfe0b88a2dcf (patch) | |
| tree | c55c7cc2767abe4a4ae0479ee566f164822cd225 /yarns | |
| parent | 00d8426f5503fbe2c2f828beb8cfd5a82716f2d6 (diff) | |
| download | obnam-85554d3567f2b00dad4b97b1cfd2dfe0b88a2dcf.tar.gz | |
Fix yarns to check for gpg error from old version
It seems CentOS 6 has a version of gpg that says "No secret key"
instead of "secret key not available". Fixed yarns to check for that.
Reported-by: Dennis Jacobfeuerborn
Diffstat (limited to 'yarns')
| -rw-r--r-- | yarns/0060-encryption.yarn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/yarns/0060-encryption.yarn b/yarns/0060-encryption.yarn index f0a95ced..acbade88 100644 --- a/yarns/0060-encryption.yarn +++ b/yarns/0060-encryption.yarn @@ -100,7 +100,7 @@ client, should not be able to access the data. WHEN user U3 attempts to restore their latest generation in repository R into X3 THEN the attempt failed with exit code 1 AND the error message matches "R0C79EX: gpg failed" - AND the error message matches "secret key not available" + AND the error message matches "secret key not available\|No secret key" (The error message above indicates that there's a bug in Obnam, which is that the error message, when an encryption is not provided but the @@ -113,7 +113,7 @@ not have access to another client's data. GIVEN a user U2 calling themselves U1 WHEN user U2 attempts to restore their latest generation in repository R into X4 THEN the attempt failed with exit code 1 - AND the error message matches "secret key not available" + AND the error message matches "secret key not available\|No secret key" Replace a key for a client -------------------------- |