Go to file
Mitchell Hashimoto 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
api api: use /v1 prefix 2015-03-13 12:53:08 -07:00
command command/unseal: tests 2015-03-13 20:17:55 -07:00
helper helper/backend: start acceptance test framework 2015-03-14 17:18:19 -07:00
http http: make TestServer public 2015-03-13 12:53:09 -07:00
physical physical: fix failing test 2015-03-12 14:30:31 -07:00
scripts scripts 2015-03-03 23:14:18 -08:00
shamir vault: sanity check key length 2015-03-12 11:20:38 -07:00
vault vault: public TestCoreUnsealed, don't modify key in Unseal 2015-03-14 17:47:11 -07:00
website website: imageoptim 2015-03-13 12:58:21 -07:00
.gitattributes Initial commit 2015-02-24 16:15:59 -08:00
.gitignore command/init 2015-03-13 12:53:08 -07:00
LICENSE Initial commit 2015-02-24 16:15:59 -08:00
Makefile scripts 2015-03-03 23:14:18 -08:00
README.md Initial commit 2015-02-24 16:15:59 -08:00
commands.go command/seal-status 2015-03-13 12:53:09 -07:00
main.go basic main boilerplate stuff 2015-03-03 23:03:24 -08:00
main_test.go basic main boilerplate stuff 2015-03-03 23:03:24 -08:00
version.go basic main boilerplate stuff 2015-03-03 23:03:24 -08:00

README.md

vault

Bits go in, bits go out. Can't explain that.