9324db7979
Vault SSH: verify echo test
2015-08-18 16:48:50 -07:00
ed258f80c6
Vault SSH: Refactoring and fixes
2015-07-10 18:44:31 -06:00
89a0e37a89
Vault SSH: Backend and CLI testing
2015-07-10 16:18:02 -06:00
3c7dd8611c
Vault SSH: Test case skeleton
2015-07-10 09:56:14 -06:00
541014e315
logical: remove SetLogger method
2015-06-30 17:39:39 -07:00
41b72a4d39
vault: provide view to backend initializer for setup
2015-06-30 17:30:43 -07:00
4ec685dc1a
Logging authentication errors and bad token usage
2015-06-18 18:30:18 -07:00
8ee5aebb3c
vault: testing raw responses
2015-05-27 14:19:12 -07:00
95c8001388
Disable mlock in tests
2015-04-28 22:18:00 -04:00
6218c2729d
http: audit endpoints
2015-04-01 18:36:13 -07:00
aba7fc1910
http: auth handlers
2015-03-31 20:24:51 -07:00
e9a3a34c27
vault: tests passing
2015-03-29 16:18:08 -07:00
4cacaf62f0
http: support auth
2015-03-29 16:14:54 -07:00
20c2375352
vault: Adding ACL enforcement
2015-03-24 11:37:07 -07:00
9d84e7bacc
vault: don't copy the key so it can be zeroed, document, add helper
2015-03-14 18:25:55 -07:00
866b91d858
vault: public TestCoreUnsealed, don't modify key in Unseal
...
/cc @armon - I do a key copy within Unseal now. It tripped me up for
quite awhile that that method actually modifies the param in-place and I
can't think of any scenario that is good for the user. Do you see any
issues here?
2015-03-14 17:47:11 -07:00
f43a0290cf
vault: public testing methods
2015-03-13 12:53:09 -07:00
vishalnayak