open-vault/vault/seal_test.go
ncabatoff 1c98152fa0
Shamir seals now come in two varieties: legacy and new-style. (#7694)
Shamir seals now come in two varieties: legacy and new-style. Legacy
Shamir is automatically converted to new-style when a rekey operation
is performed. All new Vault initializations using Shamir are new-style.

New-style Shamir writes an encrypted master key to storage, just like
AutoUnseal. The stored master key is encrypted using the shared key that
is split via Shamir's algorithm. Thus when unsealing, we take the key
fragments given, combine them into a Key-Encryption-Key, and use that
to decrypt the master key on disk. Then the master key is used to read
the keyring that decrypts the barrier.
2019-10-18 14:46:00 -04:00

47 lines
1.1 KiB
Go

package vault
import (
"context"
"reflect"
"testing"
)
// TestDefaultSeal_Config exercises Shamir SetBarrierConfig and BarrierConfig.
// Note that this is a little questionable, because we're doing an init and
// unseal, then changing the barrier config using an internal function instead
// of an API. In other words if your change break this test, it might be more
// the test's fault than your changes.
func TestDefaultSeal_Config(t *testing.T) {
bc := &SealConfig{
SecretShares: 4,
SecretThreshold: 2,
}
core, _, _ := TestCoreUnsealed(t)
defSeal := NewDefaultSeal(nil)
defSeal.SetCore(core)
err := defSeal.SetBarrierConfig(context.Background(), bc)
if err != nil {
t.Fatal(err)
}
newBc, err := defSeal.BarrierConfig(context.Background())
if err != nil {
t.Fatal(err)
}
if !reflect.DeepEqual(*bc, *newBc) {
t.Fatal("config mismatch")
}
// Now, test without the benefit of the cached value in the seal
defSeal = NewDefaultSeal(nil)
defSeal.SetCore(core)
newBc, err = defSeal.BarrierConfig(context.Background())
if err != nil {
t.Fatal(err)
}
if !reflect.DeepEqual(*bc, *newBc) {
t.Fatal("config mismatch")
}
}