summaryrefslogtreecommitdiff
path: root/yarns/0060-encryption.yarn
AgeCommit message (Collapse)AuthorFilesLines
2015-10-11encryption_plugin: add a gnupghome configuration optionBen Boeckel1-0/+16
Signed-off-by: Ben Boeckel <mathstuf@gmail.com>
2015-03-24Fix yarns to check for gpg error from old versionLars Wirzenius1-2/+2
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
2014-03-27Separate adding to share and owner stepsLars Wirzenius1-3/+3
2014-03-26Add scenario for replacing client keyLars Wirzenius1-0/+27
2014-03-21Fix test suite failures on TMPDIR without user xattrLars Wirzenius1-4/+4
Remove use of extended attributes from some tests. Make the remaining tests be conditional on whether extended attributes actually work in the temporary directory (in the user.* namespace).
2014-03-13Improve error message when secret key missingLars Wirzenius1-1/+2
The actual gpg error message is now shown, instead of hidden behind a "unknown tag found" message.
2014-02-17Fix parsing of filtered filesLars Wirzenius1-1/+1
This bug was originally triggered by the test suite, because the error message in the code had a typo. While looking for that I noticed that the code that was parsing the code seemed fishy. This is now cleaner. First of all, I split the error messages for "unknown tag" and "no tag". Then I rewrote the loop that parses so it is robust against error situations. Then I tweaked the yarn test so it now works.
2014-01-26Fix file restore, add xattr value change testLars Wirzenius1-3/+3
The single file restore test had a bug, in that it was depending on various test steps to execute fast enough that the wall clock did not advance to the next second. This has been fixed by allowing manifests to be done on single files instead of just directories. Add a test for an extended attribute value changing, and that being the only change in the live data. The backup needs to notice that it has changed. This was intended to be the original change in this commit, but I ran into the test bug above, so I had to fix that too. I was too lazy to detangle the two sets of changes for commits.
2014-01-12Fix test suite failureLars Wirzenius1-1/+1
Depending on how the encrypted data is, the error message, when accessing an encrypted repository without encryption enabled, may be different. Deal with it.
2014-01-12Add scenario for remove-clientLars Wirzenius1-1/+14
2014-01-12Note untested encryption commandsLars Wirzenius1-5/+4
2014-01-12Add note about bad error messageLars Wirzenius1-0/+5
2014-01-12More encryption testsLars Wirzenius1-3/+48
2014-01-12Basic encrypted backup/restore testLars Wirzenius1-0/+84
This sets up a whole lot of infrastructure, too.